From: Taylor Blau <me@ttaylorr.com>
To: Elijah Newren <newren@gmail.com>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
Git Mailing List <git@vger.kernel.org>,
Derrick Stolee <stolee@gmail.com>, Taylor Blau <me@ttaylorr.com>,
Jonathan Tan <jonathantanmy@google.com>
Subject: Re: Is fetch.writeCommitGraph (and thus features.experimental) meant to work in the presence of shallow clones?
Date: Wed, 15 Apr 2020 18:47:34 -0600 [thread overview]
Message-ID: <20200416004734.GA36156@syl.local> (raw)
In-Reply-To: <CABPp-BE+bC8aECT4Ak_kSObXV-euq7vCnYeUYBEjYmW4Pko=rw@mail.gmail.com>
On Wed, Apr 15, 2020 at 03:54:09PM -0700, Elijah Newren wrote:
> On Wed, Apr 15, 2020 at 1:54 PM Jonathan Nieder <jrnieder@gmail.com> wrote:
> >
> > Hi,
> >
> > Elijah Newren wrote:
> >
> > > I was building a version of git for internal use, and thought I'd try
> > > turning on features.experimental to get more testing of it. The
> > > following test error in the testsuite scared me, though:
> > >
> > > t5537.9 (fetch --update-shallow):
> > >
> > > ...
> > > + git fetch --update-shallow ../shallow/.git refs/heads/*:refs/remotes/shallow/*
> > > remote: Enumerating objects: 18, done.
> > > remote: Counting objects: 100% (18/18), done.
> > > remote: Compressing objects: 100% (6/6), done.
> > > remote: Total 16 (delta 0), reused 6 (delta 0), pack-reused 0
> > > Unpacking objects: 100% (16/16), 1.16 KiB | 1.17 MiB/s, done.
> > > From ../shallow/
> > > * [new branch] master -> shallow/master
> > > * [new tag] heavy-tag -> heavy-tag
> > > * [new tag] light-tag -> light-tag
> > > error: Could not read ac67d3021b4319951fb176469d7732e6914530c5
> > > error: Could not read ac67d3021b4319951fb176469d7732e6914530c5
> > > error: Could not read ac67d3021b4319951fb176469d7732e6914530c5
> > > fatal: unable to parse commit ac67d3021b4319951fb176469d7732e6914530c5
> > >
> > > Passing -c fetch.writeCommitGraph=false to the fetch command in that
> > > test makes it pass.
> >
> > Oh! Thanks for checking this. At $DAYJOB this was the week we were
> > going to roll out features.experimental. Time to roll that back...
> >
> > How did you go about the experiment? Does Taylor's patch make it pass?
>
> Yes, Taylor's patch makes the experiment pass. My experiment was
> pretty simple; modify the code so that features.experimental defaults
> to true:
I'm glad to hear that it is passing now. I would like to have Jonathan
Tan chime in on whether or not this patch is making sense, but if so,
I'll prepare it for real and send it out.
Thanks,
Taylor
prev parent reply other threads:[~2020-04-16 0:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-14 20:22 Is fetch.writeCommitGraph (and thus features.experimental) meant to work in the presence of shallow clones? Elijah Newren
2020-04-14 20:31 ` Taylor Blau
2020-04-14 20:31 ` Derrick Stolee
2020-04-14 23:50 ` Taylor Blau
2020-04-15 0:07 ` Taylor Blau
2020-04-15 11:55 ` Derrick Stolee
2020-04-15 15:55 ` Taylor Blau
2020-04-15 18:07 ` Elijah Newren
2020-04-16 2:05 ` Jonathan Tan
2020-04-15 20:54 ` Jonathan Nieder
2020-04-15 22:54 ` Elijah Newren
2020-04-16 0:47 ` Taylor Blau [this message]
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=20200416004734.GA36156@syl.local \
--to=me@ttaylorr.com \
--cc=git@vger.kernel.org \
--cc=jonathantanmy@google.com \
--cc=jrnieder@gmail.com \
--cc=newren@gmail.com \
--cc=stolee@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.