Re: Fetching upstream remote fails if repo was a blobless clone

From: Jeff King <peff@peff.net>
Date: Aug 2, 2025, 09:32 UTC
Message-ID: <20250802093226.GF3711639@coredump.intra.peff.net>
In-Reply-To: <CAB=S_8+LMsSpnRWQZwK2Dj63WdcPy1vp+aJ=erDbf_aaPoU3cA@mail.gmail.com>

On Fri, Aug 01, 2025 at 05:30:56AM -0400, Justin Su wrote:

Show 5 quoted lines

> git clone --filter=blob:none git@github.com:injust/delta
> cd delta/
> git remote add upstream git@github.com:dandavison/delta
> git fetch upstream
> [...]

Show 10 quoted lines

> ```
> remote: Enumerating objects: 1578, done.
> remote: Counting objects: 100% (776/776), done.
> remote: Compressing objects: 100% (15/15), done.
> remote: Total 1578 (delta 772), reused 761 (delta 761), pack-reused 802 (from 2)
> Receiving objects: 100% (1578/1578), 2.67 MiB | 5.34 MiB/s, done.
> Resolving deltas: 100% (1156/1156), completed with 356 local objects.
> fatal: did not receive expected object 0020d54b979cc8cf59a13406f98bfe515b190559
> fatal: fetch-pack: invalid index-pack output
> ```

Hmm. I can't reproduce here, but I wonder if it is dependent on the server-side repo state. E.g., if it depends on the fetch from the upstream remote receiving a delta against a blob from origin. And that might change if the server repacks, or even if there is another push.

Is it still happening for you?

-Peff