git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
Paul Smith <paul@mad-scientist.net>
Date
Jun 2, 2023, 19:12 UTC
Message-ID
<7aa2ab6714bd14671ba9cfff611dea2fa088c99e.camel@mad-scientist.net>
In-Reply-To
<b6f210da2c3cc7746b984b797ad89687cba2d1f8.camel@mad-scientist.net>
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.

Previous: Paul SmithNext: rsbecker@nexbridge.com
Message 2 of 14 in “Anyone know why git ls-remote output might be corrupted?”
  1. Paul SmithJun 2, 2023
  2. Paul SmithJun 2, 2023
  3. rsbecker@nexbridge.comJun 2, 2023
  4. Paul SmithJun 2, 2023
  5. rsbecker@nexbridge.comJun 2, 2023
  6. Paul SmithJun 2, 2023
  7. Elijah NewrenJun 3, 2023
  8. Elijah NewrenJun 3, 2023
  9. Jeff KingJun 4, 2023
  10. Jeff KingJun 4, 2023
  11. Jeff KingJun 4, 2023
  12. Paul SmithJun 9, 2023
  13. Junio C HamanoJun 9, 2023
  14. Paul SmithJun 12, 2023

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.