On Thu, Oct 01, 2020 at 03:09:35PM -0400, David A Case wrote:
> On Thu, Oct 01, 2020, Scott Le Grand wrote:
>
> >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.
>
> Could it be an http: protocol problem?
>
> Have you tried git clone git.gitlab.ambermd.org:amber/amber.git ?
>
> (Right now I'm only on a slowish wifi connection, so cannot check
> myself).
That's the way i always do it, and it just took 2.5 minutes:
Oct 01 3:04:55pm pitzer.osc.edu 106$ /tmp git clone git.gitlab.ambermd.org:amber/amber.git amber &; sleep 1; 700 amber
[1] 8219
Cloning into 'amber'...
remote: Enumerating objects: 508655, done.
remote: Total 508655 (delta 0), reused 0 (delta 0), pack-reused 508655
Receiving objects: 100% (508655/508655), 2.76 GiB | 36.11 MiB/s, done.
Resolving deltas: 100% (388669/388669), done.
Checking out files: 100% (40493/40493), done.
[1] Done git clone git.gitlab.ambermd.org:amber/amber.git amber
160.623u 17.559s 2:32.85 116.5% 0k shared+0k 64+16402704io 0pf+0w 1251676k max mem
scott
_______________________________________________
AMBER-Developers mailing list
AMBER-Developers.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber-developers
Received on Thu Oct 01 2020 - 12:30:02 PDT
