From: Shawn Pearce <spearce@spearce.org>
To: git <git@vger.kernel.org>
Subject: git push keeps writing after server failure
Date: Fri, 12 Jun 2015 10:31:33 -0700 [thread overview]
Message-ID: <CAJo=hJvzjnLFhF4REBzX=pgFamBfu7hZeZidy_8Rmi_DwwR4Nw@mail.gmail.com> (raw)
I did something stupid like trying to push a copy of WebKit[1] into my
GitHub account. This is ~5.2 GiB of data, which GitHub prefers not to
accept. Ok ...
$ git push --all git@github.com:spearce/wk.git
Counting objects: 2752427, done.
Delta compression using up to 12 threads.
Compressing objects: 100% (442684/442684), done.
remote: fatal: pack exceeds maximum allowed size
Writing objects: 100% (2752427/2752427), 5.28 GiB | 8.86 MiB/s, done.
Total 2752427 (delta 2225007), reused 2752427 (delta 2225007)
fatal: The remote end hung up unexpectedly
fatal: The remote end hung up unexpectedly
Notice GitHub prints "remote: fatal: pack exceeds maximum allowed
size". That interrupted my "Writing objects" progress meter, and then
git push just kept going and wrote really really fast (170 MiB/s!)
until the entire pack was sent.
A similar thing happens on https:// if the remote HTTP server goes
away in the middle of sending the pack. Except its slower to send the
remainder of the pack before git push finally terminates with an
error.
Shouldn't git push realize its stream is broken and stop writing when
the peer is all like "uh, no, I'm not going to do that, but thanks for
trying"?
[1] https://webkit.googlesource.com/WebKit/
next reply other threads:[~2015-06-12 17:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-12 17:31 Shawn Pearce [this message]
2015-06-12 17:57 ` git push keeps writing after server failure Junio C Hamano
2015-06-12 18:12 ` Jeff King
2015-06-12 18:20 ` Jeff King
2015-06-12 18:50 ` 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
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='CAJo=hJvzjnLFhF4REBzX=pgFamBfu7hZeZidy_8Rmi_DwwR4Nw@mail.gmail.com' \
--to=spearce@spearce.org \
--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.
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).