Alerts send on non-existing problems

[isametal88]

Describe the issue

Hello,

we are facing something that is probably a configuration issue, but we're not able to figure it out.

We are using Weblate to manage the translation of both our web app and our mobile app, but every single day we receive at least two alerts:

• the web project sends : Repository outdated.
  The VCS repository is not up to date with the upstream one. Please merge changes manually or set up hooks to automate this. (of course the hooks are configured, everything is working properly, we never sync the updates manually)

• the mobile project: Parse error
  Error message
  No such file or directory
  Failing file
  src/localizations/it.json
  (of course also this is wrong: the file exists and it's the source of our translation, which is working)

We have no idea on what to do with this alerts, could somebody help us out?

Thank you very much

I already tried

• I've read and searched the documentation.
• I've searched for similar issues in this repository.

Steps to reproduce the behavior

No response

Expected behavior

No response

Screenshots

No response

Exception traceback

No response

How do you run Weblate?

Docker container

Weblate versions

No response

Weblate deploy checks

No response

Additional context

No response

[github-actions]

This issue looks more like a support question than an issue. We strive to answer these reasonably fast, but purchasing the support subscription is not only more responsible and faster for your business but also makes Weblate stronger.

In case your question is already answered, making a donation is the right way to say thank you!

[nijel]

"Repository outdated" is triggered nightly whenever there are commits in the upstream repository missing in Weblate one. If you update Weblate repo nightly and not on push via webhook, this can easily be triggered, but later removed once you update it. You can increase REPOSITORY_ALERT_THRESHOLD to make it happen less likely.

"No such file or directory" maybe the file was not present in some revision? It can only happen when parsing the file and it is not present.

[isametal88]

Hello Nijel,

no, the updates from our repo is pushed directly. Most of the e-mails show a conflict, but it's not true (we tried also to reset the weblate repo to have a clean state, but nothing has changed).
And the "no such file or directory" is impossible because it's the same localization json weblate uses to read the strings that are being translated :-(

Isaia

[nijel]

Maybe two Weblate processes are running with a different configuration?

[isametal88]

Hello,

I'll investigate about this, but I don't think that's the case.

Isaia

[github-actions]

This issue has been automatically marked as stale because there wasn’t any recent activity.

It will be closed soon if no further action occurs.

Thank you for your contributions!