You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm having many lock file exists error in System Notices. I know it's likely because sync requests are triggered too quickly (I have a Github app that triggers it on every Github webhook), and it doesn't cause anything. But is there way to reduce the errors? Like using a retry logic, using a queue, etc.
Failed to update mirror repository '/data/git/repositories/harryzcy/repo.git': fatal: Unable to create '/data/git/repositories/harryzcy/repo.git/./objects/info/commit-graphs/commit-graph-chain.lock': File exists.
Another git process seems to be running in this repository, e.g.
an editor opened by 'git commit'. Please make sure all processes
are terminated then try again. If it still fails, a git process
may have crashed in this repository earlier:
remove the file manually to continue.
Gitea Version
1.21.7
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
Git Version
No response
Operating System
No response
How are you running Gitea?
Kubernetes with distributed storage
Database
PostgreSQL
The text was updated successfully, but these errors were encountered:
Description
I'm having many lock file exists error in System Notices. I know it's likely because sync requests are triggered too quickly (I have a Github app that triggers it on every Github webhook), and it doesn't cause anything. But is there way to reduce the errors? Like using a retry logic, using a queue, etc.
Gitea Version
1.21.7
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
Git Version
No response
Operating System
No response
How are you running Gitea?
Kubernetes with distributed storage
Database
PostgreSQL
The text was updated successfully, but these errors were encountered: