-
-
Notifications
You must be signed in to change notification settings - Fork 266
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
Error: the repository you want to access is already locked #1014
Comments
If you are sure there is no other process, you can delete But realistically, only another git-bug process would put a lock there, which begs the question: if there really is no other process running, why does git-bug think so? The corresponding code is there: git-bug/util/process/process.go Line 9 in 1ae31b3
Admittedly, there is a TODO that could explain your problem, but you are the first one to report a problem with that. |
Sorry, finally I made a reboot : it works now, but I don't know how to reproduce... So issue could be closed. |
Here I reproduced: |
That's a very good point. I suppose we need a reliable and multi-platform way to check that the running process is indeed git-bug. Now, how to do that ... |
May process.Name or process.NameWithContext should do the trick ? |
I'm busy with other things, so anyone would be faster than that :-) |
That's a pretty crazy path to a bug - I'm running Linux so I never hard kill anything (or reboot for that matter). What OS are you running and when you say that you start |
I did a bit of testing (Xubuntu Linux 22.04) and found that the lock file is not always removed when I would have expected:
I wouldn't expect that we can capture SIGKILL but the |
I'm runnig Linux (6.1.12-arch1-1), using |
Hi,
Lauching Git Bug (v0.8.0) gives me this Error message:
Error: the repository you want to access is already locked by the process pid 1138
I don't have any 1138 PID running, and Git is working fine (Guitar, Gitk, etc.)
Is there a way to unlock ?
The text was updated successfully, but these errors were encountered: