From: Google — Mergify Date: Mon, 16 Nov 2026 11:45:52 GMT Subject: [BUG] partial clone lazy-fetches a blob it just wrote (bisected to 5946a564cd) Message-ID: <69EF6B53-E153-46CC-B7EC-536BEBE8CF52@mergify.com> 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: Auto-merging dev-tools/go.mod Auto-merging go.mod Auto-merging testing/go.mod [bp fatal: remote error: upload-pack: not our ref 201d4490be49318c26485d10869070ae44d3e7ef fatal: could not fetch 929ed29a43110d65cb7d581c4028e3f183088c3c from promisor remote The commit itself has been written. The failure happens while the commit summary is printed. 201d4490 is the result of the content merge of dev-tools/go.mod. It is stored as a loose object in the clone, and "git cat-file -t" with GIT_NO_LAZY_FETCH=1 reports it as a blob after the failure. Reproduction (needs network access to github.com, takes a few seconds): git init -q repro && cd repro git config core.repositoryformatversion 1 git config user.name t && git config user.email t@example.com git remote add origin https://github.com/elastic/fleet-server git config remote.origin.promisor true git config remote.origin.partialclonefilter blob:none git sparse-checkout set --no-cone --stdin dirs; dir; dir = dir->next) { - if (retry) + if (retry) { odb_source_prepare(&dir->packed->base, ODB_PREPARE_FLUSH_CACHES); + odb_source_prepare(&dir->loose->base, ODB_PREPARE_FLUSH_CACHES); + } This is a check, not a proposed fix. Updating the loose cache when an object is written may be the better fix. I'm happy to test patches against this reproduction. We run git this way in production (blob:none partial clones, cherry-pick, merge-tree). This hit cherry-picks in several unrelated public and private repositories, and on each repository it fails the same way on every attempt. We have gone back to 2.53 until this is fixed.