From: Sergio Durigan Junior <sergiodj@sergiodj.net>
To: Duy Nguyen <pclouds@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Possible race condition with git-rebase + .git/index.lock
Date: Tue, 12 Mar 2019 12:45:26 -0400 [thread overview]
Message-ID: <877ed459eh.fsf@sergiodj.net> (raw)
In-Reply-To: <CACsJy8ANLkz=3cj1dAuHdUCkrgQzos=90EEG0n901o3QAp3PUQ@mail.gmail.com> (Duy Nguyen's message of "Tue, 12 Mar 2019 17:28:15 +0700")
On Tuesday, March 12 2019, Duy Nguyen wrote:
> On Tue, Mar 12, 2019 at 5:18 AM Sergio Durigan Junior
> <sergiodj@sergiodj.net> wrote:
>> This works without problems most of the time (well, usually there are
>> conflicts and all, but that's a burden I have to carry). However,
>> sometimes I notice that git fails with:
>>
>> # 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.
>
> Is the output this clean? What I'm looking for is signs of automatic
> garbage collection kicking in the middle of the rebase. Something like
> "Auto packing the repository blah blah for optimum performance".
Yeah, this is the exact output. I also thought about "git gc", but I
don't see any output related to it. Is it possible that it's being
executed in the background and not printing anything?
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/
next prev parent reply other threads:[~2019-03-12 16:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-11 21:38 Possible race condition with git-rebase + .git/index.lock Sergio Durigan Junior
2019-03-11 22:50 ` Eric Sunshine
2019-03-11 22:53 ` Sergio Durigan Junior
2019-03-12 10:28 ` Duy Nguyen
2019-03-12 16:45 ` Sergio Durigan Junior [this message]
2019-03-12 19:23 ` Elijah Newren
2019-03-12 19:32 ` Sergio Durigan Junior
2019-03-12 19:39 ` Elijah Newren
2019-03-12 19:58 ` Sergio Durigan Junior
2019-03-13 20:40 ` Phillip Wood
2019-03-13 20:48 ` Sergio Durigan Junior
2019-03-13 20:59 ` Jeff King
2019-03-13 21:07 ` Sergio Durigan Junior
2022-10-28 16:04 ` Possible race condition with git-rebase + .git/index.lock - probably a gettext issue Mingun
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877ed459eh.fsf@sergiodj.net \
--to=sergiodj@sergiodj.net \
--cc=git@vger.kernel.org \
--cc=pclouds@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.