From: Jeff King <peff@peff.net>
Date: Fri, 09 Oct 2020 17:55:06 GMT
Subject: Re: 2.29.0.rc0.windows.1: Duplicate commit id error message when fetching
Message-ID: <20201009175506.GA957408@coredump.intra.peff.net>
In-Reply-To: <64de22fd-2e1b-aaab-3a8e-f6f1d630a46e@gmail.com>

On Fri, Oct 09, 2020 at 01:46:07PM -0400, Derrick Stolee wrote:

> > Can you reproduce it if you do
> > 
> > git config core.commitGraph false
> > git config fetch.writeCommitGraph true
> > ?
> 
> I _can_ repro it in this case! I think there must be something
> very interesting going on where the commit-graph is parsed in
> _some_ places, but not in others. This is something that I can
> really start to dig into.

Here's a much more minimal reproduction:

  git init repo
  cd repo

  git commit --allow-empty -m one
  git rev-parse HEAD |
  git -c core.commitGraph=false \
      commit-graph write --split=no-merge --stdin-commits
  git rev-parse HEAD |
  git -c core.commitGraph=false \
      commit-graph write --split=no-merge --stdin-commits

  git commit --allow-empty -m two
  git rev-parse HEAD |
  git commit-graph write --split --stdin-commits

The final write will die() with the "unexpected duplicate" message.

-Peff