All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Steinhardt <ps@pks.im>
To: Jeff King <peff@peff.net>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Oct 2025, #12; Thu, 30)
Date: Tue, 4 Nov 2025 13:40:15 +0100	[thread overview]
Message-ID: <aQn0LyW248iNDpkf@pks.im> (raw)
In-Reply-To: <20251103213059.GA2528366@coredump.intra.peff.net>

On Mon, Nov 03, 2025 at 04:30:59PM -0500, Jeff King wrote:
> On Mon, Nov 03, 2025 at 12:10:47PM -0800, Junio C Hamano wrote:
> 
> > Junio C Hamano <gitster@pobox.com> writes:
> > 
> > > Bisect points at 054f5f45 (ref-filter: parse objects on demand,
> > > 2025-10-23), which is unfortunate, as that is the motivating step of
> > > the whole topic.
> > 
> > Here is a fairly simple reproduction.  It appears that this does not
> > require the refs to be packed (i.e., "t7004-tag.sh -i -v" fails
> > after saying "*** Loose ***" here, without moving to the packed
> > test).

Oof.

> I think the issue is that nobody ever resets data->maybe_object. So it
> is left cached with the very first object that gets looked up.
> 
> Something like this seems to fix it, but there may be a better place to
> do the reset.

Yeah, I think this makes sense. I'd attribute the root cause here to the
fact that both `oi` and `oi_peeled` are global variables. I didn't
realize that and thought it would be populated for every reference
individually, but that's obviously not the case.

Only thing I'd change is to instead call `get_object()`, which is the
entry point for `grab_values()`.

Will send a patch in a bit, thanks both!

Patrick

      reply	other threads:[~2025-11-04 12:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-30 21:36 What's cooking in git.git (Oct 2025, #12; Thu, 30) Junio C Hamano
2025-10-31  6:42 ` Patrick Steinhardt
2025-10-31 15:51   ` Junio C Hamano
2025-10-31 17:33   ` Eric Sunshine
2025-11-03 14:50     ` Lucas Seiki Oshiro
2025-11-03 17:57   ` Junio C Hamano
2025-11-03 18:43     ` Junio C Hamano
2025-11-03 20:10       ` Junio C Hamano
2025-11-03 21:30         ` Jeff King
2025-11-04 12:40           ` Patrick Steinhardt [this message]

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=aQn0LyW248iNDpkf@pks.im \
    --to=ps@pks.im \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=peff@peff.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.