Skip to content

Correct translation workflow #280

Closed

Description

@freakboy3742

Describe the bug

The automated translation workflow has been failing since October 8.

It appears that there has been a change on the Weblate server that makes it susceptible to errors when running wlc lock then wld commit in rapid succession - the "commit" triggers a "HTTP error 423: Locked {'detail': 'Another repository operation is already in progress.'}" error.

How to reproduce the bug

See CI logs for recent translation attemps.

The "skipped" runs are expected; the most recent failure is an example of a failure. The build for "Add Goatcounter analytics. (#278)" is the last successful build.

Minimum example code

Screenshots

No response

Environment details

  • Operating system and version: Github Actions

Logs


Additional context

This problem was also seen on the website; it was corrected with beeware/beeware.github.io#836 and beeware/beeware.github.io#837.

There's one other unrealted modification in the beeware.github.io translate workflow that should be copied over while we're in the file - the if condition governing the entire workflow operation has an additional github.repository clause on the website repository. That clause should be copied (and updated as appropriate) as part of fixing the locking issue.

Activity

  1. moved this from To triage to Ready in BeeWare Planningon Oct 15, 2026
  2. aaravgauba commented on Oct 19, 2026

    @aaravgauba
    Contributor

    I would like to work on this. Thank You.

  3. moved this from Ready to In progress in BeeWare Planningon Oct 24, 2026
  4. moved this from In progress to Done in BeeWare Planningon Oct 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions