From: Derrick Stolee <stolee@gmail.com>
To: Gary Oberbrunner <garyo@oberbrunner.com>, git@vger.kernel.org
Subject: Re: Fwd: Possible git bug in commit-graph: "invalid commit position"
Date: Mon, 20 Jan 2020 19:37:40 -0500 [thread overview]
Message-ID: <d4313777-ce8c-0b64-997e-17cb719c9ab8@gmail.com> (raw)
In-Reply-To: <CAFChFyi5J-mb+rshtF7U2m=MtPzEPUa+V1_qbEXC=-LdQ218yA@mail.gmail.com>
On 1/20/2020 12:32 PM, Gary Oberbrunner wrote:
> I'm running git 2.24.1 on Linux/WSL, and sometimes git fails with this error:
> ```
> % git diff --cached
> fatal: invalid commit position. commit-graph is likely corrupt
> ```
> Usually that error goes away after I do a few more git operations, but
> I haven't been able to discern a pattern yet. It's not always with
> "diff", can be any git command as far as I can tell.
> Perhaps it started after I enabled the commit-graph stuff:
> ```
> [core]
> editor = emacsclient -c -a \"\"
> preloadindex = true
> fscache = true
> autocrlf = false
> commitGraph = true
> writeCommitGraph = true
> ```
> In fact, when I turn off `commitGraph`, the error goes away. But as I
> say, sometimes it goes away of its own accord.
Disabling the featuere will definitely remove the error. Some commands may
also just not "visit" the corrupt commit.
> Googling turns up almost nothing on this error. I have no idea if I've
> done something wrong to corrupt the commit graph, or if it's a git
> bug. If there's anything I can do to help debug it, I'd be happy to --
> just let me know.
Please run "git commit-graph verify" to see if that catches the
corruption. If not, then the verify feature is broken.
Then, you can delete your .git/objects/info/commit-graph file
and rebuild it with "git commit-graph write". (If you have
fetch.writeCommitGraph enabled, then you may need to instead
delete the .git/objects/info/commit-graphs directory.) If that
process does not fix the problem, then there is definitely a bug
in the feature. At the moment, it may just be a flipped bit in
the file.
Thanks,
-Stolee
next prev parent reply other threads:[~2020-01-21 0:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAFChFygiaMsUJC5Kfpnk26DLWbY0gPdNJpZ_gLMf4utZ6_oZxA@mail.gmail.com>
2020-01-20 17:32 ` Fwd: Possible git bug in commit-graph: "invalid commit position" Gary Oberbrunner
2020-01-21 0:37 ` Derrick Stolee [this message]
2020-02-04 22:33 ` Gary Oberbrunner
2020-05-15 12:03 ` Alex Riesen
2020-06-21 20:45 ` Michael Forney
2020-06-22 13:45 ` Derrick Stolee
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=d4313777-ce8c-0b64-997e-17cb719c9ab8@gmail.com \
--to=stolee@gmail.com \
--cc=garyo@oberbrunner.com \
--cc=git@vger.kernel.org \
/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 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 NNTP newsgroup(s).