Re: Possible race condition with git-rebase + .git/index.lock
- From
- Sergio Durigan Junior <sergiodj@sergiodj.net>
- Date
- Mar 11, 2019, 22:53 UTC
- Message-ID
- <87bm2h58fy.fsf@sergiodj.net>
- In-Reply-To
- <CAPig+cS_NLgwr6F2OqMpMZ3GBO-Cyru3G3UBxiT4ULJ_V1Bqvg@mail.gmail.com>
On Monday, March 11 2019, Eric Sunshine wrote:
Show 16 quoted lines
> On Mon, Mar 11, 2019 at 6:17 PM Sergio Durigan Junior > <sergiodj@sergiodj.net> wrote: >> # 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).
This is on GNU/Linux (Fedora 28, to be specific). I haven't had the chance to test this on other distros, unfortunately. And since it seems to be a race condition, it's kind of hard to perform tests that trigger this.
Thanks,
-- Sergio GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36 Please send encrypted e-mail if possible http://sergiodj.net/