fatal: Unable to create '/path/to/repo/.git/index.lock': File exists.

[Cyberbeni]

Occasionally when I bring Fork to the foreground and press the Commit and Push button immediately, I will get the error mentioned in the title. This is probably caused by the automatic fetch (triggered by bringing the app to the foreground) creating a lock file and the commit command being started without waiting for it to finish (Because retrying the commit right after always works). I think it would be better to wait for previous commands in the same repo to complete.

There is also a similar error when I "Commit and Push" and then immediately want to "Push and create pull request" which would also be solved by serialising these commands.

[octogonz]

I also get this message constantly. It seems to be caused by Fork itself, due to a previous Git command that is still running in the background.

Please test Fork on huge repos. 🙂 This problems probably don't happen much in small repos.

[DanPristupov]

@octogonz consider enabling fs-monitor in git git fsmonitor--daemon start.
#1591

[octogonz]

Nice, I'll give it a try!

For anyone following along, looks like git config --local core.fsmonitor true launches the daemon automatically.

[octogonz]

@DanPristupov After enabling the daemon, I am still getting these errors. Maybe it is a little bit less often?

Fork should implement some kind of internal queue that avoids spawning conflicting git processes.

[iTris666]

+1 on big git repro you often have this if you try to commit for instance while the status of git-fork is still refreshing. simply waiting for the refresh when such a command if asked would be great.

[DanPristupov]

We made an improvement in Fork 2.30.

[shah-aditya]

Is v2.30 available for Windows? I am currently on v1.91.2.0