[AMBER-Developers] git clone http://gitlab.ambermd.org/amber/amber.git fails bigly after 1GB or so...

From: Scott Le Grand <varelse2005.gmail.com>
Date: Thu, 1 Oct 2020 11:56:25 -0700

I have been trying to clone the AMBER repo since yesterday. And it would
appear the gitlab server is barfing on 1 GB or larger transfers now.

I have tried this on 3 machines, 2 at home, and one from within NVIDIA so I
really don't think this is me...

Long story short, debugging crap on:
remote: Compressing objects: 100% (28712/28712), done.
11:04:33.745512 pkt-line.c:80 packet: sideband< PACK ...
11:04:33.745555 run-command.c:334 trace: run_command:
'--shallow-file' '/home/slegrand/amber/amber/.git/shallow.lock'
'index-pack' '--stdin' '-v' '--fix-thin' '--keep=fetch-pack 27850 on zeus'
11:04:33.745753 exec_cmd.c:120 trace: exec: 'git' '--shallow-file'
'/home/slegrand/amber/amber/.git/shallow.lock' 'index-pack' '--stdin' '-v'
'--fix-thin' '--keep=fetch-pack 27850 on zeus' '--pack_header=2,41159'
11:04:33.746466 git.c:344 trace: built-in: git 'index-pack'
'--stdin' '-v' '--fix-thin' '--keep=fetch-pack 27850 on zeus'
* Connection #2 to host gitlab.ambermd.org left intact MiB/s
11:13:10.458343 pkt-line.c:80 packet: git< 0000
fatal: The remote end hung up unexpectedly
fatal: early EOF
fatal: index-pack failed

I've tried shallow transfers and sparse checkouts and I have run out of


Nope, still fails past 1 GB...

PostBuffer size tricks on the clone request?

Nope, still fails just past 1 GB.

Kinda blocked right now. Has anyone encountered this?

AMBER-Developers mailing list
Received on Thu Oct 01 2020 - 12:00:02 PDT
Custom Search