Re: Possible race condition with git-rebase + .git/index.lock
- From
Eric Sunshine <sunshine@sunshineco.com>
- Date
- Mar 11, 2019, 22:50 UTC
- Message-ID
- <CAPig+cS_NLgwr6F2OqMpMZ3GBO-Cyru3G3UBxiT4ULJ_V1Bqvg@mail.gmail.com>
- In-Reply-To
- <87k1h55bx0.fsf@sergiodj.net>
On Mon, Mar 11, 2019 at 6:17 PM Sergio Durigan Junior <sergiodj@sergiodj.net> wrote:
Show 9 quoted lines
> # git rebase origin/master > ... > Applying: commitX > Applying: commitY > Applying: commitZ > fatal: Unable to create '/home/xyz/dir1/dir2/.git/index.lock': File exists. > > The first thing I did was to check whether the index.lock file existed, > but it doesn't.
What platform is this on? If Windows, I'm wondering if something (such as a virus scanner) is holding the lock file open long enough to prevent Git from actually deleting it (and perhaps Git doesn't notice the failed deletion -- until the next time it tries to take the lock).