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

Re: Did we break receive-pack recently?

From
Brandon Casey <drafnel@gmail.com>
Date
Aug 6, 2012, 01:37 UTC
Message-ID
<CA+sFfMcA2qUcigPg_ijWJmiTKYY9V4f4f6XQp8xT76wLaUXSxA@mail.gmail.com>
In-Reply-To
<7vk3xe6r1w.fsf@alter.siamese.dyndns.org>
On Sat, Aug 4, 2012 at 6:55 PM, Junio C Hamano <gitster@pobox.com> wrote:
Show 19 quoted lines
> I just saw this:
>
>     $ git push ko
>     ko: Counting objects: 332, done.
>     Delta compression using up to 4 threads.
>     Compressing objects: 100% (110/110), done.
>     Writing objects: 100% (130/130), 32.27 KiB, done.
>     Total 130 (delta 106), reused 21 (delta 20)
>     Auto packing the repository for optimum performance.
>     fatal: protocol error: bad line length character: Remo
>     error: error in sideband demultiplexer
>     To ra.kernel.org:/pub/scm/git/git.git
>     ...
>
> What is unusual with this push is that it happened to trigger the
> auto-gc on the receiving end and the message "Auto packing the
> repository..." came back to the pusher just fine, but somebody
> nearby seem to have tried to say "Remo"(te---probably) without
> properly using the sideband.
Or perhaps "Remo" is short for "Removing...".
Perhaps this is the source:
   $ grep Remo builtin/prune.c
   printf("Removing stale temporary file %s\n", fullpath);
-Brandon
Previous: Junio C HamanoNext: Brandon Casey
Message 2 of 15 in “Did we break receive-pack recently?”
  1. Junio C HamanoAug 5, 2012
  2. Brandon CaseyAug 6, 2012
  3. Brandon CaseyAug 6, 2012
  4. 1/2 t/t5400: demonstrate breakage caused by informational message from pruneBrandon Casey, Aug 7, 2012
  5. 2/2 prune.c: only print informational message in show_only or verbose modeBrandon Casey, Aug 7, 2012
  6. Junio C HamanoAug 7, 2012
  7. Junio C HamanoAug 7, 2012
  8. Brandon CaseyAug 7, 2012
  9. Jeff KingAug 7, 2012
  10. Brandon CaseyAug 7, 2012
  11. Junio C HamanoAug 7, 2012
  12. Junio C HamanoAug 7, 2012
  13. Jeff KingAug 7, 2012
  14. Brandon CaseyAug 7, 2012
  15. Jeff KingAug 7, 2012

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.