{"thread":{"id":"49454","subject":"wrong output on fail","startedAt":"2018-09-29T03:33:19Z","lastAt":"2018-10-03T02:25:08Z","messageCount":2,"participants":["Paul Wratt","Jeff King"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"359265","messageId":"CA+zYZ3-CS1ZP_LXdWPMVoOvcU+4QimJH2A0WgQ2yT5dFkO5F3Q@mail.gmail.com","threadId":"49454","inReplyTo":null,"subject":"wrong output on fail","fromName":"Paul Wratt","fromEmail":"paul.wratt@gmail.com","sentAt":"2018-09-29T03:30:21Z","receivedAt":"2018-09-29T03:33:19Z","isPatch":false,"sender":{"key":"paul.wratt@gmail.com","avatar":null},"body":"--------------\n...\nTotal 21 (delta 8), reused 0 (delta 0)\nerror: RPC failed; result=56, HTTP code = 0\nfatal: The remote end hung up unexpectedly\nfatal: The remote end hung up unexpectedly\nEverything up-to-date\n--------------\n\nI am getting the above from \"git push\".\n\nI am having intermittent HTTPS connection failures with my ISP\n(Vodafone NZ, mobile), although HTTP works fine. It may even be a\npeering issue.\n\nThe failures above are accounted for, but that last line is definitely wrong\n\nCheers\nPaul\n"},{"id":"359491","messageId":"20181003022502.GD20553@sigill.intra.peff.net","threadId":"49454","inReplyTo":"CA+zYZ3-CS1ZP_LXdWPMVoOvcU+4QimJH2A0WgQ2yT5dFkO5F3Q@mail.gmail.com","subject":"Re: wrong output on fail","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2018-10-03T02:25:03Z","receivedAt":"2018-10-03T02:25:08Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Sat, Sep 29, 2018 at 03:30:21PM +1200, Paul Wratt wrote:\n\n> --------------\n> ...\n> Total 21 (delta 8), reused 0 (delta 0)\n> error: RPC failed; result=56, HTTP code = 0\n> fatal: The remote end hung up unexpectedly\n> fatal: The remote end hung up unexpectedly\n> Everything up-to-date\n> --------------\n> \n> I am getting the above from \"git push\".\n> \n> I am having intermittent HTTPS connection failures with my ISP\n> (Vodafone NZ, mobile), although HTTP works fine. It may even be a\n> peering issue.\n> \n> The failures above are accounted for, but that last line is definitely wrong\n\nYes, that's unfortunate. Usually we'd complain if the connection drops,\nbut I wonder if this has to do with the extra trip through\ngit-remote-https. I.e., that program sees the failure and dies, but we\ndon't manage to pass back the error code to the main git-push process.\n\nIt sounds like this is repeatable? If so, can you try with GIT_TRACE=1\nand GIT_TRANSPORT_HELPER_DEBUG=1 set in the environment?\n\n-Peff\n"}]}