Re: git push keeps writing after server failure

On Fri, Jun 12, 2015 at 02:20:45PM -0400, Jeff King wrote: > > > 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 en

Re: git push keeps writing after server failure

On Fri, Jun 12, 2015 at 02:12:56PM -0400, Jeff King wrote: > > $ git push --all g...@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 siz

Re: git push keeps writing after server failure

On Fri, Jun 12, 2015 at 10:31:33AM -0700, Shawn Pearce wrote: > 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 ... Heh, yeah. We cap it at 2G, and if you are going to have a WebKit fork, w

Re: git push keeps writing after server failure

Shawn Pearce writes: > 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 ... > ... > Shouldn't git push realize its stream is broken and stop writing when > the peer is all like "uh, no, I'm

git push keeps writing after server failure

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 g...@github.com:spearce/wk.git Counting objects: 2752427, done. Delta compression using up to 12 threads. Compressing objects