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

Re: git push keeps writing after server failure

From
Junio C Hamano <gitster@pobox.com>
Date
Jun 12, 2015, 17:57 UTC
Message-ID
<xmqqtwucdd31.fsf@gitster.dls.corp.google.com>
In-Reply-To
<CAJo=hJvzjnLFhF4REBzX=pgFamBfu7hZeZidy_8Rmi_DwwR4Nw@mail.gmail.com>
Shawn Pearce <spearce@spearce.org> writes:
Show 7 quoted lines
> I did something stupid like trying to push a copy of WebKit[1] into my
> GitHub account. This is ~5.2 GiB of data, which GitHub prefers not to
> accept. Ok ...
> ...
> Shouldn't git push realize its stream is broken and stop writing when
> the peer is all like "uh, no, I'm not going to do that, but thanks for
> trying"?

Nice wish, but I am not sure if we are structured to do that easily. The "fatal:" message is going on the sideband that is demultiplexed by a separate async "sideband-demux" thread and pack_objects() is oblivious to what is being said on the error channel #2.

Previous: Shawn PearceNext: Jeff King
Message 2 of 5 in “git push keeps writing after server failure”
  1. Shawn PearceJun 12, 2015
  2. Junio C HamanoJun 12, 2015
  3. Jeff KingJun 12, 2015
  4. Jeff KingJun 12, 2015
  5. Jeff KingJun 12, 2015

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.