uptime-kuma
uptime-kuma copied to clipboard
Weblate alert of too many outgoing commits
⚠️ Please verify that this bug has NOT been raised before.
- [X] I checked and didn't find similar issue
🛡️ Security Policy
- [X] I agree to have read this project Security Policy
📝 Describe your problem
Problem
Just recived an alert email saying
The VCS repository has many changes compared to the upstream. Please merge the changes manually or set up push to automate this.
Also ⚠️ appears on the Component and on all the language in it, which is so annoying.
As I checked that there are no conflict, I did a manully push, and the alert disappered.
Reason
After searching weblate docs, I figured out that alert emails would be send when outgoing (or missing) commits is great than set value(REPOSITORY_ALERT_THRESHOLD, default to 25). Which make sence as #2713 has 29 commits.
Solutions
Following method may solve the problem.
- merge language file changes frequently on github
- improve the REPOSITORY_ALERT_THRESHOLD
- change the
Merge style
of vcs tomerge
(I personally dislike that, as rebase give us a clean commit tree) - set smaller push interval, but
Merge style
required to bemerge
, asrebase
will lead to force-push - other solutions? idk
🐻 Uptime-Kuma Version
latest
💻 Operating System and Arch
latest
🌐 Browser
latest
🐋 Docker Version
latest
🟩 NodeJS Version
latest
Will try to set REPOSITORY_ALERT_THRESHOLD later. But as our previous experience, those env vars are not working for Docker?
But as our previous experience, those env vars are not working for Docker?
I except REPOSITORY_ALERT_THRESHOLD
to work with docker, as there is no related settings of it in docker setting code. Just search in that file for REPOSITORY_ALERT_THRESHOLD with no result.
Have set a large number, hope this works.
Have set a large number, hope this works.
Oh no, it alert me again🤔
Not have so much free time recently to learn about weblate's code logic, so not sure the reason why it doesn't work.
To save our time, just change the Merge style
to merge
on weblate vcs setting would be an easy solution.
Though I have the permission on weblate, I expect your approval of doing such operation, or you can just do it yourself.
Have set a large number, hope this works.
Oh no, it alert me again🤔
Yes... those env vars are not usable in the docker container, just like the GITHUB_CREDENTIALS
. Only env vars listed here could be used: https://docs.weblate.org/en/latest/admin/install/docker.html
Will try to use merge
method
Yes... those env vars are not usable in the docker container, just like the
GITHUB_CREDENTIALS
. Only env vars listed here could be used: https://docs.weblate.org/en/latest/admin/install/docker.html
It's possible to edit configuration beyond environment variables by overriding settings from the data volume
Will try to use
merge
method
It doesn't work, so I have changed back to rebase
for clean commit tree previously.
New alert shows up recently, and I manually resolve it every time the alert shows up :disappointed:
We are clearing up our old issues and your ticket has been open for 3 months with no activity. Remove stale label or comment or this will be closed in 2 days.
This issue was closed because it has been stalled for 2 days with no activity.
It's possible to edit configuration beyond environment variables by overriding settings from the data volume
@louislam
Have you tried this method to setup REPOSITORY_ALERT_THRESHOLD
? I receive those alert email basically everyday, which is so annoying.
We are clearing up our old help
-issues and your issue has been open for 60 days with no activity.
If no comment is made and the stale label is not removed, this issue will be closed in 7 days.