From: Taylor Blau <me@ttaylorr.com>
To: "herr.kaste" <herr.kaste@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: BUG: commit-graph.c:1068 when doing `git pull`
Date: Thu, 12 Nov 2020 09:42:53 -0500 [thread overview]
Message-ID: <X61J7bWDXO/r7Ob5@nand.local> (raw)
In-Reply-To: <CAFzd1+7VxaGGMVKicuy8KnWdZoBxEHY8xS9kK1VF0Tgai=Kcxg@mail.gmail.com>
Hi Caspar,
On Mon, Nov 02, 2020 at 08:12:07PM +0100, herr.kaste wrote:
> A
>
> $ git commit-graph write
>
> did the trick.
>
> Let me know if you think there could be something useful to reproduce,
> somewhere.
I think this is worth trying to reproduce. The first message you're
seeing about the commit-graph-chain.lock already existing is a
red-herring: it's likely that the last time you tried to generate a
commit-graph, that it hit that same BUG() and left the stale lock laying
around. (I can't remember off the top of my head whether we still run
the atexit handlers upon a BUG(), but even still, I could believe that
some other stray process left it laying around, too).
So, what's interesting is why your commit graph ended up in a state that
it got some commit without all of its parents. If you could reproduce
that state, that would be interesting.
Are you using shallow or partial clones?
> Regards
> Caspar Duregger
>
> Am Mo., 2. Nov. 2020 um 19:30 Uhr schrieb herr.kaste <herr.kaste@gmail.com>:
> >
> > Hi all!
> >
> > I'm stuck with this error message
> >
> > $ git pull
> > BUG: commit-graph.c:1068: missing parent
> > 104f5eb377763b2ed9663e8949aed265b69f000f for commit
> > c59ed9b7b6d4268ae6cb1069a9b51e02ad9aa1d8
> >
> > This happens since the last `fetch --prune origin`.
> >
> > If I do it again, I get
> >
> > $ git pull
> > fatal: Unable to create 'C:/Users/c-flo/AppData/Roaming/Sublime
> > Text 3/Packages/GitSavvy/.git/objects/info/commit-graphs/commit-graph-chain.lock':
> > File exists.
> > ...
> >
> > And upon removing that file, I get the first error message again.
> >
> > I actually don't know yet how to move on from here. I'm stuck, so I
> > appreciate any help.
> >
> > $ git --version
> > git version 2.29.2.windows.1
> >
> >
> > Regards
> > Caspar Duregger
Thanks,
Taylor
next prev parent reply other threads:[~2020-11-12 14:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-02 18:30 BUG: commit-graph.c:1068 when doing `git pull` herr.kaste
2020-11-02 19:12 ` herr.kaste
2020-11-12 14:42 ` Taylor Blau [this message]
2020-11-12 16:27 ` Ævar Arnfjörð Bjarmason
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=X61J7bWDXO/r7Ob5@nand.local \
--to=me@ttaylorr.com \
--cc=git@vger.kernel.org \
--cc=herr.kaste@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).