Closed stanislav-brabec closed 3 years ago
And a minor suggestion: remote HTTP responses like 429, 500, 503, 504 and similar possibly temporary replies should not trigger immediate mails to all project/component subscribers. It makes sense to report it after several failed attempts.
Thank you for your report; the issue you have reported has just been fixed.
I am experiencing this error e-mail randomly, often several similar mails at once:
Broken repository browser URL
This component is set up incorrectly.
The repository browser URL points to non-existing locations:
Looking at the log, it happened i the time, when several robots were crawling Weblate in parallel and several users were browsing, and one user did complicated searches.
It seems that GitHub introduces on decreased the limit. Weblate should reflect it and decrease frequency of source browser URL checks.
Looking into the localmessages, I see:
The first error is correct, the rest is unexpected.
To Reproduce the issue
It is not easy to reproduce. It appears randomly, once per several days or weeks.
Server configuration and status
Weblate installation: openSUSE Leap 15.3 + dedicated repositories.
weblate list_versions
Weblate deploy checks
weblate check --deploy
Additional context
I am not sure, whether GitHub counts only direct accesses, or also accesses with Referrer.
Analyzing the web crawler logs, I suggest to enhance robots.txt with:
and maybe