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

Re: Cryptic error messages?

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 22, 2009, 21:14 UTC
Message-ID
<7vws9c1jdz.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<20090422205006.GE14146@coredump.intra.peff.net>
Jeff King <peff@peff.net> writes:
Show 13 quoted lines
> On Wed, Apr 22, 2009 at 04:32:51PM -0400, Jeff King wrote:
>
>>   3. receive-pack notices that the unpacker failed, and spews
>> 
>>        error: unpack failed: unpacker exited with error code
>> 
>>      to stderr, in case unpack-objects didn't say anything.
>
> Actually, this is not true. receive-pack actually passes the error code
> back to send-pack, which prints it. I think it is doing so because we
> get that status separate from the individual ref status. But if you look
> at receive-pack, it doesn't even bother trying individual refs if the
> unpack failed; every ref will just get the "unpack failed" message.

How could it even "bother" to tell which ref? The protocol says "Here are the values for the refs after you unpack the data that follows; here is the pack data for you", and then you find the error in the pack data.

Previous: Jeff KingNext: Jeff King
Message 6 of 8 in “Cryptic error messages?”
  1. John DlugoszApr 20, 2009
  2. Dmitry PotapovApr 21, 2009
  3. John DlugoszApr 21, 2009
  4. Jeff KingApr 22, 2009
  5. Jeff KingApr 22, 2009
  6. Junio C HamanoApr 22, 2009
  7. Jeff KingApr 22, 2009
  8. John DlugoszApr 22, 2009

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.