-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Garbage-Collection not working #10299
Comments
We should give a different context from the default so that it has a longer timeout. |
Or run it in background withot any timeout. |
I've done a basic implementation on my fork (aswild@7db9db3) though it could be enhanced by firing a System Notice when complete. |
This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions. |
This issue has been automatically closed because of inactivity. You can re-open it if needed. |
How is the status here? My hope was to get this in 1.12.0. |
This was reported as fixed by #10745 |
I've tested it with 1.12.0
|
@somera did you adjust the settings in https://docs.gitea.io/en-us/config-cheat-sheet/#cron---repository-health-check-cronrepo_health_check |
I tested this in 1.12.x. And it works if I set the timeout higher. Thx! |
[x]
):Description
Im starting GC in the admin dashboard ("Garbage-Collection auf Repositories ausführen"). I'm hosting 929 repositories. After start this operation I see on the monitoring page, that GC is running. But after some time the admin dashboard shows
Repository garbage collection failed: Error: context deadline exceeded
...
Screenshots
The text was updated successfully, but these errors were encountered: