-
-
Notifications
You must be signed in to change notification settings - Fork 6k
Clean up the lock files created 24 hours ago #35399
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
base: main
Are you sure you want to change the base?
Conversation
I guess this may be an acceptable workaround but I ultimately I think it's a bug in git if it leaves stale lockfiles around (assuming we only use git commands to add those remotes). |
It’s not a Git bug. The Git subprocess may exit abnormally or be canceled if Gitea shuts down, reboots, or exits unexpectedly. |
Ok, and git does not offer any commands to clean up lockfiles, right? It has to be done with manual deletion? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can try it I guess
Not right. You can't hard-code these lock file names. |
Why not? The lock files in a Git repository are stored at fixed relative locations. Traversing the entire repository just to find them would be inefficient. |
Related to #32018