Another problem with inconsistency checking

[tomkolp]

After adding new files and translating automatically, the consistency check does not work as expected.

1 Adds several components that share common segments (same context and source)
2 I run automatic translation manually

Common strings are marked as an inconsistency. After the automatic translation is finished, there is no more inconsistency, but the check is still there. I have to manually run checking for each file separately. Checking the entire project is not necessary because it takes several days. Usually adds more than 100 files at once.

I think calling checks for a specific component list would solve the problem.

[nijel]

I've added tests to cover this in 241901e, and it seems to work correctly there.

[nijel]

The code I've added does test the batch checks update. Is translation propagation enabled on all your components?

[tomkolp]

Propagation is enabled throughout the project. This only happens after manually triggered automatic translation. There is no problem with normal translation.
I got the names of all the components from the list via api and created a script that manually runs the checks:

#! / bin / sh
docker-compose exec --user weblate weblate weblate updatechecks eso-crack / reapers-march-ezzags-bandits
docker-compose exec --user weblate weblate weblate updatechecks eso-crack / reapers-march-how-few-remain
.....
.....

This fixed all the checks in the entire component list.

[nijel]

The check’s update is supposed to happen in the background, so it might take some time. Or it might crash and that would appear in the logs only (unless you have configured Sentry).

[tomkolp]

I have sentry configured, I did not notice any errors a few hours after automatic translation.
The next time I add new files I will wait longer and see if the checking starts.

[tomkolp]

Today five hours ago, I used automatic translation on 60 files. The files contain some strings with the same context and source as files already present in the project. After 5 hours, checking was not started. Sentry did not record any problems at this time. I have the latest version bleeding from today.
Edit:
After 14 hours, the check started. Is this time so long because the project is huge? Ultimately, the project will be three times larger.