-
-
Notifications
You must be signed in to change notification settings - Fork 5.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PR are not checked #14311
Comments
So I think this error is because of a slow start of your persistent queue for prs. There is very likely a problem with the persistent level db queue that backs up pr checking. The reason you're seeing this is because of a race in the Has() function for the queue. I will put up a PR to fix that race and mark it as fixing this issue - however, that will merely displace the problem to the real problem you're seeing - which is very likely that you've corrupted your persistent queues. If I had to make a bet as to the reason why that happens - its because you're kill -9ing gitea which you should not do. |
There is potentially a race with a slow starting internal queue causing a NPE if Has is checked before the internal queue has been setup. This PR adds a lock on the Has() fn. Fix go-gitea#14311 Signed-off-by: Andrew Thornton <art27@cantab.net>
Hello Since last discussion and evolve with binary, I don't use anymore kill -9 action. And I've tried to clean queue directory and was not working. |
There is potentially a race with a slow starting internal queue causing a NPE if Has is checked before the internal queue has been setup. This PR adds a lock on the Has() fn. Fix #14311 Signed-off-by: Andrew Thornton <art27@cantab.net>
Backport go-gitea#14651 There is potentially a race with a slow starting internal queue causing a NPE if Has is checked before the internal queue has been setup. This PR adds a lock on the Has() fn. Fix go-gitea#14311 Signed-off-by: Andrew Thornton <art27@cantab.net>
[x]
):Description
All PR are blocked in stale state.
When we force pr_patch_checker with on process. We get previous error. A restart is needed
First log when we set 1 process to 5minutes, second when unlimited time.
The text was updated successfully, but these errors were encountered: