From: aleksandrs@ledovskis.lv
Date: Thu, 13 Jun 2019 09:30:23 GMT
Subject: Re: Git status parse error after v.2.22.0 upgrade
Message-ID: <20190613093023.GA3919@ariake.ledovskis.lv>
In-Reply-To: <nycvar.QRO.7.76.6.1906122046400.789@QRFXGBC-DHN364S.ybpnyqbznva>

Hello,

Managed to repro this problem on my private repo too.

Bisect points to b51a0fdc3822c2ef260f6d496b6df6d33b101e8a
However, I think the real culprit is 4a72486de97b5c6b0979b2b51e50c268bdb0d4f6, specifically `parse_insn_line` call.

My repo indeed contains a ".git/sequencer/todo" file which contains references to commits long-gone (i.e., rebased).
Renaming or deleting this file stops whines about "error: could not parse".

--
Regards,
Aleksandrs Ļedovskis

On Wed, Jun 12, 2019 at 08:47:27PM +0200, Johannes Schindelin wrote:
> Hi Espen,
> 
> On Wed, 12 Jun 2019, Espen Antonsen wrote:
> 
> > I don't have any hooks, just the default sample scripts. GIT_TRACE
> > doesn't show anything else.
> 
> Okay, it was just a guess.
> 
> And here is another guess: unless you impart with more details about your
> test case, I guess there is little anybody else can do to help you.
> 
> Ciao,
> Johannes