New locale in existing (Sicilian, Mozilla accounts) stuck on "Not synced yet"

[flodolo]

Locale was added a few days ago (around Jan 10), but it's still showing up as "Not synced yet".

A manual sync doesn't show any error in the logs. Even a forced sync didn't make the project show up as available.

[flodolo]

Correction: a forced sync made the project available, I didn't realize it was still going (scheduled sync started in the meantime, making the log confusing).

[ezgiayvazoglu]

we also can not sync, we committed the latest database as json files in the corresponding repository, but in pontoon we are seeing them as missing translations and also approve all is not working for these.
without any addition in pontoon, we just updated the database by our own(via git commit) and we can not see the new translations on UI after the "sync", although it is just deleting the missing ones even they exist in the jsons.

[eemeli]

@flodolo Do I understand right that the issue here is that with a pre-existing project, a newly added locale is not showing up as available until a forced sync is run?

@ezgiayvazoglu Does that description match your problem as well, or are you having some other issue with sync? If not, then it would be best to file a separate issue with a more detailed description.

[flodolo]

@flodolo Do I understand right that the issue here is that with a pre-existing project, a newly added locale is not showing up as available until a forced sync is run?

That's correct.

[ezgiayvazoglu]

@eemeli yes it was the same at the beginning, when we want to sync, it was staying like "Not synced yet", but then it's fixed somehow. I don't know what is the the "force sync" but, we needed to change ssh key to reconnect and it was worked. for the resting, we can open a new issue, thanks

[flodolo]

Forced sync is done via command line

./manage.py sync_projects --projects PROJECT_ID --force

[eemeli]

I was able to replicate the issue locally, and looking at what's going on, the crux is that we currently lack a way to detect a locale being added.

I think we ought to track changes being made to project config, with something like a dirty flag or a last_modified timestamp. This is similar to #3494, though the solutions could be different.

@mathjazz I'm out of my depth figuring out how pontoon.administration.views.manage_project() actually works; it feels so very Django. Do you think you could take this on? The first-pass idea here would be to make a note somewhere when the project config changes, and if it does, do the next sync for the project with force=True.

[mathjazz]

I was able to replicate the issue locally, and looking at what's going on, the crux is that we currently lack a way to detect a locale being added.

I think we ought to track changes being made to project config, with something like a dirty flag or a last_modified timestamp. This is similar to #3494, though the solutions could be different.

That's essentially #2708?

@mathjazz I'm out of my depth figuring out how pontoon.administration.views.manage_project() actually works; it feels so very Django.

That's very mildly put. Admin code is not in a great shape (still mild), mostly due to constant pushback of #2021.

Do you think you could take this on? The first-pass idea here would be to make a note somewhere when the project config changes, and if it does, do the next sync for the project with force=True.

That doesn't sound optimal. We should only sync relevant locales, and ignore other changes to project configuration.

Check out how the old sync handled that:

pontoon/pontoon/sync/tasks.py

Lines 262 to 263 in f369337

	# Store newly added locales and locales with newly added resources
	new_locales = []