From: Patrick Steinhardt <ps@pks.im>
To: "Google — Mergify" <remy.duthu@mergify.com>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [BUG] partial clone lazy-fetches a blob it just wrote (bisected to 5946a564cd)
Date: Mon, 16 Nov 2026 13:46:00 +0100 [thread overview]
Message-ID: <avr7CP29sPOdS5DE@pks.im> (raw)
In-Reply-To: <69EF6B53-E153-46CC-B7EC-536BEBE8CF52@mergify.com>
Hi,
On Mon, Nov 16, 2026 at 12:45:52PM +0100, Google — Mergify wrote:
> Since Git 2.54.0, a cherry-pick in a blob:none partial clone can try to
> lazy-fetch a blob that the cherry-pick has just written to the local
> object store. The server never had that blob, so the fetch fails and the
> command dies:
I think this is a known issue and there's a fix in-flight at [1]. Could
you please test that change and verify that it fixes the issue for you?
Thanks!
Patrick
[1]: <20261104-pks-odb-loose-stale-cache-v1-0-a00d5cdb5e7d@pks.im>
next prev parent reply other threads:[~2026-11-16 12:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-16 11:45 [BUG] partial clone lazy-fetches a blob it just wrote (bisected to 5946a564cd) Google — Mergify
2026-11-16 12:46 ` Patrick Steinhardt [this message]
[not found] ` <8F838F35-E5D5-4F6C-8835-99D1C040E0D4@mergify.com>
2026-11-16 20:16 ` Patrick Steinhardt
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=avr7CP29sPOdS5DE@pks.im \
--to=ps@pks.im \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=remy.duthu@mergify.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox