git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff King <peff@peff.net>
To: Paul Wratt <paul.wratt@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: wrong output on fail
Date: Tue, 2 Oct 2018 22:25:03 -0400	[thread overview]
Message-ID: <20181003022502.GD20553@sigill.intra.peff.net> (raw)
In-Reply-To: <CA+zYZ3-CS1ZP_LXdWPMVoOvcU+4QimJH2A0WgQ2yT5dFkO5F3Q@mail.gmail.com>

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

      reply	other threads:[~2018-10-03  2:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-29  3:30 wrong output on fail Paul Wratt
2018-10-03  2:25 ` Jeff King [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20181003022502.GD20553@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=paul.wratt@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).