From: <rsbecker@nexbridge.com>
To: <paul@mad-scientist.net>, <git@vger.kernel.org>
Subject: RE: Anyone know why git ls-remote output might be corrupted?
Date: Fri, 2 Jun 2023 15:34:06 -0400 [thread overview]
Message-ID: <000501d99589$358d4850$a0a7d8f0$@nexbridge.com> (raw)
In-Reply-To: <7aa2ab6714bd14671ba9cfff611dea2fa088c99e.camel@mad-scientist.net>
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?
next prev parent reply other threads:[~2023-06-02 19:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-02 18:59 Anyone know why git ls-remote output might be corrupted? Paul Smith
2023-06-02 19:12 ` Paul Smith
2023-06-02 19:34 ` rsbecker [this message]
2023-06-02 19:53 ` Paul Smith
2023-06-02 20:02 ` rsbecker
2023-06-02 20:12 ` Paul Smith
2023-06-03 1:17 ` Elijah Newren
2023-06-03 1:12 ` Elijah Newren
2023-06-04 6:00 ` Jeff King
2023-06-04 6:25 ` Jeff King
2023-06-04 6:30 ` Jeff King
2023-06-09 15:33 ` Paul Smith
2023-06-09 18:58 ` Junio C Hamano
2023-06-12 19:59 ` Paul Smith
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='000501d99589$358d4850$a0a7d8f0$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=git@vger.kernel.org \
--cc=paul@mad-scientist.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).