# wrong output on fail 2 messages from 2018-09-29 to 2018-10-03. Participants: Paul Wratt, Jeff King. Thread: https://gitlist.dev/t/49454 ## Paul Wratt, 2018-09-29 03:30 Subject: wrong output on fail Message-ID: URL: https://gitlist.dev/e/CA%2BzYZ3-CS1ZP_LXdWPMVoOvcU%2B4QimJH2A0WgQ2yT5dFkO5F3Q%40mail.gmail.com ``` -------------- ... 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 Cheers Paul ``` ## Jeff King, 2018-10-03 02:25 Subject: Re: wrong output on fail Message-ID: <20181003022502.GD20553@sigill.intra.peff.net> URL: https://gitlist.dev/e/20181003022502.GD20553%40sigill.intra.peff.net In-Reply-To: ``` On Sat, Sep 29, 2018 at 03:30:21PM +1200, Paul Wratt wrote: > -------------- > ... > 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 ```