I tried cloning just the repo and then fetching all of trac and it worked. My git version seems to be more recent though, the output is all different. Have you tried increasing the post buffer?
git config --global http.postBuffer 524288000 git fetch -v On Friday, June 12, 2015 at 10:46:18 PM UTC+2, Emmanuel Charpentier wrote: > > Things seem still flaky now (22:42 CET) : git fetch still hangs. But git > fetch -v gives some signs of life before hanging : > > git fetch -v > POST git-upload-pack (gzip 12481 to 6253 bytes) > POST git-upload-pack (gzip 13031 to 6539 bytes) > POST git-upload-pack (gzip 14581 to 7322 bytes) > POST git-upload-pack (gzip 17231 to 8652 bytes) > POST git-upload-pack (gzip 22731 to 11443 bytes) > POST git-upload-pack (gzip 33681 to 17013 bytes) > POST git-upload-pack (gzip 56631 to 28499 bytes) > POST git-upload-pack (gzip 103581 to 51743 bytes) > POST git-upload-pack (gzip 148331 to 73896 bytes) > POST git-upload-pack (gzip 199231 to 99039 bytes) > POST git-upload-pack (gzip 228286 to 113433 bytes) > error: RPC failed; result=22, HTTP code = 500 > fatal: The remote end hung up unexpectedly > > Is there anything I can do at my end to fix this ? Or pray for Malaysian > to recover reason (an possibly sacrificing another manager) ? > > -- > Emmanuel Charpentier > > > > Le vendredi 12 juin 2015 11:16:41 UTC+2, Volker Braun a écrit : >> >> I've seen it now, too. The connection is pretty flaky even when it works, >> e.g. massive packet loss (look at the sequence numbers): >> >> >> $ ping trac.sagemath.org >> PING trac.sagemath.org (128.208.178.249): 56 data bytes >> 64 bytes from 128.208.178.249: seq=6 ttl=46 time=512.834 ms >> 64 bytes from 128.208.178.249: seq=7 ttl=46 time=514.608 ms >> 64 bytes from 128.208.178.249: seq=9 ttl=46 time=475.129 ms >> 64 bytes from 128.208.178.249: seq=15 ttl=46 time=512.305 ms >> 64 bytes from 128.208.178.249: seq=27 ttl=46 time=478.100 ms >> 64 bytes from 128.208.178.249: seq=29 ttl=46 time=476.673 ms >> >> >> Tracing it, the problem seems to originate at the Telia -> Level3 >> boundary. So there is nothing we can do, just wait for the big guys to fix >> it. >> >> >> On Friday, June 12, 2015 at 11:04:17 AM UTC+2, Nathann Cohen wrote: >>> >>> Desperately trying to push something, the function hangs. I also cannot >>> get to load the ticket I want to update [1] :-P >>> >>> Nathann >>> >>> [1] http://trac.sagemath.org/ticket/18681 >>> >> -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
