On Thu, Nov 05, 2026 at 02:43:14PM -0500, Jeff King wrote:
On Wed, Nov 04, 2026 at 01:16:35PM +0100, Patrick Steinhardt wrote:
quoted
This issue can cause git-merge(1) to die in a partial clone because we
try to fetch an object that we have just written, as reported in [1]:
1. `prefetch_for_content_merges()` performs quick existence checks for
all blobs that need a content merge to figure out which ones need
to be fetched from the promisor remote. These lookups populate the
loose object cache for the respective sharding directories.
2. We lazily fetch the missing blobs, which writes a new packfile.
3. We perform the merge and write the resulting blobs as loose
objects. The cache is not updated, so for all blobs whose sharding
directory was populated in (1), the object existence checks will
fail.
4. When checking out the merge result, `prefetch_cache_entries()`
performs existence checks for all index entries that need to be
written to the worktree. But due to the stale cache, the merged
blobs are reported as missing, and consequently we try to fetch
them from the promisor remote. This fetch fails because the remote
will most likely not have them.
I don't doubt this sequence of events, but it feels like it is pointing
to a separate underlying bug.
Anybody who is passing QUICK should be prepared to get a false negative
and recover reasonably. That's what QUICK is for. And anybody who is not
passing QUICK will not use the cache (as you note, they do not use the
cache at all, but it would also be reasonable to use it and fall back to
a refresh).
So it sounds like somebody is using QUICK who should not be in this
path. At first glance, it makes sense for prefetch_cache_entries() to be
QUICK: it is just a prefetch, so it's happy to get a wrong answer.
But as we've seen, a false negative here can be a problem because it
actually tries the fetch. The most obvious issue is the one we saw here:
if the fetch fails because the object is in fact local-only, then rather
than say "oh well, I guess it is not something we can pre-fetch" we barf
at the lower level, in promisor_remote_get_direct(). It feels like that
low-level function should be informed that the caller is in "false
negatives are OK" QUICK mode and quietly return failure.
But even that is tricky. Our fetch request is all-or-nothing, so one
missing local object means we can't prefetch anything. Not great. Plus,
even a quietly-discarded fetch attempt is expensive to do, when we could
much more cheaply get the object by just looking again at the
filesystem.
So I kind of wonder if prefetch_cache_entries(), along with any caller
doing an OBJECT_INFO_FOR_PREFETCH check, ought to omit the QUICK flag.
It would mean that the normal case of having missing partial objects
(about to be fetched) would cause us to re-scan the local pack list, but
that's not _that_ expensive, especially compared to the fetch we're
about to do.
Yeah, that's a valid point. Honestly, by now I'm almost urged to just
drop the QUICK flag altogther. It's a source of bugs, and the longer we
look at it the more cases we find where the existing users thereof are
buggy in specific edge cases. We just recently removed one user of
QUICK, and this here is another dubious case. I wouldn't be surprised if
we could find edge cases for the other, remaining users, as well.
Possibly we'd want some logic to avoid doing the re-scan for every
object (so if you are about to prefetch for a million objects, you don't
want to trigger a million SECOND_READ re-scans, but rather do it once).
That would require some refactoring.
But it would fix this problem, along with any other related ones. In
particular, I think your fix here is leaving lots of cases with the same
problem. Missing our own loose write in the cache is an obvious problem,
but it's not the only reason we might fail to see a local object: it
could be in a pack now, or it could have been written as a loose object
by some _other_ process.
True. I think it's a valuable fix regardless as it ensures that our
cache reflects what we ourselves just did, so it's a simple improvement.
But there's definitely more edge cases to this whole thing.
So I suspect you could cause the same problem racily by running "git
log" on some local-only commits while somebody else is repacking, with a
sequence like:
1. git-log scans the odb and builds an internal packlist.
2. git-repack runs in another process, migrating loose objects to
packs. git-log doesn't know about our new pack.
3. git-log tries to diff a commit. In a non-partial clone, the diff
code eventually tries to read that object, realizes we can't find
it, and does a SECOND_READ. But in a partial clone, we try to
prefetch via diff_queued_diff_prefetch(). That uses the same
FOR_PREFETCH flag and will try to fetch it.
I'd guess most such cases are going to be racy, though you can imagine
ones that aren't. E.g., if mktree actually did pre-fetching, then
something like:
for fn in $files
do
oid=$(git hash-object -w $fn)
printf "100644 blob $oid\t$fn"
done |
git mktree
might run into similar problems. It needs to know about newly written
local loose objects, but they were written externally. You might even be
able to find a similar case where git-merge ends up writing the objects
via a helper process, but I didn't check.
So I dunno. This is fixing a real case and not making anything worse, so
maybe it is reasonable in the interim. But it's the tip of the iceberg,
I think.
No arguing there. I'd propose to still move ahead with this particular
fix here as it addresses the original bug report and addresses the
regression. But I agree that we may want to invest some more time into
this problem space after it lands.
quoted
We could in theory fix this by flushing all the loose object caches
again, like we used to do before 5946a564cdd. But that wouldn't address
the root cause: the cache would still be stale unless somebody does a
non-QUICK read for a missing object. Instead, fix the bug by updating
the cache whenever we write a new loose object.
I agree that the object cache flushing was only fixing this problem by
chance. But I think it might be worth reconsidering the change from
5946a564cdd. Flushing the cache (or not) should always be an
optimization problem, not a correctness one (assuming the rest of the
code is bug-free and using QUICK sensibly). But a SECOND_READ fallback
is a good indication that information about our odb is stale, and it's a
good time (from an optimization perspective) to flush them.
It may be, but it may just as well not be. In some cases we may truly
not have a specific object, and the caller would want to know about
that. And in that case we should avoid flushing to only those cases
where it's really necessary.
Patrick