Skip to content

Correct translation workflow #95

Open

Description

@freakboy3742

Describe the bug

The automated translation workflow has been failing since at least August 30.

There are two sources of error.

The first is that the Zizmor update appears to have introduced errors into the configuration such that the permissions required to commit aren't available.

The second is 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 "Translated using Weblate (Portuguese)" is the last successful build.

Minimum example code

Screenshots

No response

Environment details

  • Operating system and version: Github Actions

Logs


Additional context

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

However, the permissions issue requires other changes; the easiest approach will be to copy all of translate.yml from the website repo, updating to reference beeware-tutorial instead of beeware.github.io.

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