Re: Anyone know why git ls-remote output might be corrupted?

From: Paul Smith <paul@mad-scientist.net>
Date: Jun 2, 2023, 19:53 UTC
Message-ID: <679863bd1ed8a54b48472ad310c2bae7f274e1ec.camel@mad-scientist.net>
In-Reply-To: <000501d99589$358d4850$a0a7d8f0$@nexbridge.com>

On Fri, 2023-06-02 at 15:34 -0400, rsbecker@nexbridge.com wrote:

Show 16 quoted lines

> On Friday, June 2, 2023 3:13 PM, Paul Smith wrote:
> > On Fri, 2023-06-02 at 14:59 -0400, Paul Smith wrote:
> > > Also a bunch of the heads are missing.  It's pretty clear that
> > > right in the middle of printing one of the SHAs we suddenly lost
> > > a bunch of output, and started printing stuff from later (in the
> > > last instance 66 out of 131 heads were missing).
> > 
> > I forgot to mention: git ls-remote does not exit with an error
> > code.  The exit code is 0 (success).
> > 
> > The reason I get this failure is that as I parse the output I
> > notice that the SHA is invalid (contains a non-hex character "i")
> > and it throws this error.
> 
> Does your CI/CD system use sparse checkout or depth=1 or some other
> partial clone?

Yes, the local copy of the repo is a sparse checkout.

I'm surprised that matters to ls-remote... I would have expected that the "sparseness" of the local repo is irrelevant when listing the state of the remote's heads? Is that the reason for the issue I'm seeing?