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

Re: wrong output on fail

From
Jeff King <peff@peff.net>
Date
Oct 3, 2018, 02:25 UTC
Message-ID
<20181003022502.GD20553@sigill.intra.peff.net>
In-Reply-To
<CA+zYZ3-CS1ZP_LXdWPMVoOvcU+4QimJH2A0WgQ2yT5dFkO5F3Q@mail.gmail.com>
On Sat, Sep 29, 2018 at 03:30:21PM +1200, Paul Wratt wrote:
Show 16 quoted lines
> --------------
> ...
> Total 21 (delta 8), reused 0 (delta 0)
> error: RPC failed; result=56, HTTP code = 0
> fatal: The remote end hung up unexpectedly
> fatal: The remote end hung up unexpectedly
> Everything up-to-date
> --------------
> 
> I am getting the above from "git push".
> 
> I am having intermittent HTTPS connection failures with my ISP
> (Vodafone NZ, mobile), although HTTP works fine. It may even be a
> peering issue.
> 
> The failures above are accounted for, but that last line is definitely wrong

Yes, that's unfortunate. Usually we'd complain if the connection drops, but I wonder if this has to do with the extra trip through git-remote-https. I.e., that program sees the failure and dies, but we don't manage to pass back the error code to the main git-push process.

It sounds like this is repeatable? If so, can you try with GIT_TRACE=1 and GIT_TRANSPORT_HELPER_DEBUG=1 set in the environment?

-Peff
Previous: Paul Wratt
Message 2 of 2 in “wrong output on fail”
  1. Paul WrattSep 29, 2018
  2. Jeff KingOct 3, 2018

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.