Re: Git wire protocol v2 fails fetching shallow changes with `pack has XXX unresolved deltas` on large repos with lots of tags Inbox x

From: Arturas Moskvinas <arturas@uber.com>
Date: Oct 19, 2018, 13:58 UTC
Message-ID: <CAGY-PBiKaKwhjyHCDF5Crq6z-D17WMW5iqUjfSNiQqaHcZP0dw@mail.gmail.com>
In-Reply-To: <20181017205340.190036-1-jonathantanmy@google.com>

Hello,

Unfortunately I do not have for such step. On one of our internal repositories it is failing but unreliably when fetching from remote.

-- Arturas Moskvinas

On Wed, Oct 17, 2018 at 11:53 PM Jonathan Tan <jonathantanmy@google.com> wrote:

Show 15 quoted lines

>
> > No changes are needed in mirrored repository. Crash happens both with
> > 2.18.0 and 2.19.1 git versions. Having repository locally is not
> > required but reduces test runtime, you can quite reliably reproduce
> > issue when fetching over net directly from chromium.orgbypassing
> > mirroring step.
>
> Do you have the reproduction steps for this? If I run
>
>   git -c protocol.version=2 fetch --tags \
>     https://chromium.googlesource.com/chromium/src \
>     +refs/heads/*:refs/remotes/origin/* --depth=1
>
> repeatedly in the same repository, it succeeds. (And I've checked with
> GIT_TRACE_PACKET that it uses protocol v2.)