From: Yuri <yuri@rawbw.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: git quietly fails on https:// URL, https errors are never reported to user
Date: Fri, 17 Jan 2014 01:40:54 -0800 [thread overview]
Message-ID: <52D8FAA6.1010601@rawbw.com> (raw)
In-Reply-To: <20140116180310.GA27180@sigill.intra.peff.net>
On 01/16/2014 10:03, Jeff King wrote:
> We used to print "Reading from helper 'git-remote-https' failed" in this
> instance. But in the majority of cases, remote-https has printed a
> useful message already to stderr, and the extra line just confused
> people. The downside, as you noticed, is that when the helper dies
> without printing an error, the user is left with no message.
I would like to suggest to return this printout, see patch below. This
would be a revert of this commit:
commit 266f1fdfa99f5d29ca7ce455966e7960c00a82e4
Author: Jeff King <peff@peff.net>
Date: Fri Jun 21 03:05:39 2013 -0400
I think that in a rare case of error this extra-printout wouldn't hurt.
I also made this message more user friendly, without mentioning the term
"helper".
Yuri
diff --git a/transport-helper.c b/transport-helper.c
index 2010674..5ea2831 100644
--- a/transport-helper.c
+++ b/transport-helper.c
@@ -58,7 +58,7 @@ static int recvline_fh(FILE *helper, struct strbuf
*buffer, const char *name)
if (strbuf_getline(buffer, helper, '\n') == EOF) {
if (debug)
fprintf(stderr, "Debug: Remote helper quit.\n");
- exit(128);
+ die("Failure in '%s' protocol reader", name);
}
if (debug)
next prev parent reply other threads:[~2014-01-17 9:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-16 12:27 git quietly fails on https:// URL, https errors are never reported to user Yuri
2014-01-16 18:03 ` Jeff King
2014-01-16 19:28 ` Yuri
2014-01-17 9:40 ` Yuri [this message]
2014-01-17 19:43 ` Junio C Hamano
2014-01-17 20:13 ` Jeff King
2014-01-17 20:18 ` Jeff King
2014-01-17 20:39 ` Yuri
2014-01-17 21:10 ` Jeff King
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52D8FAA6.1010601@rawbw.com \
--to=yuri@rawbw.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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.
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 NNTP newsgroup(s).