From: Yuri <yuri@rawbw.com>
To: git@vger.kernel.org
Subject: git quietly fails on https:// URL, https errors are never reported to user
Date: Thu, 16 Jan 2014 04:27:03 -0800 [thread overview]
Message-ID: <52D7D017.107@rawbw.com> (raw)
On one of my FreeBSD systems I can't clone github through https URL.
It only says "Cloning into 'MyProject'...", writes some files, but then
deletes everything, without printing anything else at all. Exit code is 128.
Replacing https:// with git:// makes it work fine.
While debugging, I find that remove_junk() deletes all directories from
under __cxa_finalize.
Before this, exit(128) is called from recvline_fh ("Debug: Remote helper
quit.) And this function in turn is called from under
refs = transport_get_remote_refs(transport);
I think you need to make sure that any https errors (in this and other
locations) are reported to the user, and git never quits on error
without saying what the error is.
git-1.8.5.2
Yuri
next reply other threads:[~2014-01-16 12:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-16 12:27 Yuri [this message]
2014-01-16 18:03 ` git quietly fails on https:// URL, https errors are never reported to user Jeff King
2014-01-16 19:28 ` Yuri
2014-01-17 9:40 ` Yuri
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=52D7D017.107@rawbw.com \
--to=yuri@rawbw.com \
--cc=git@vger.kernel.org \
/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).