RE: With big repos and slower connections, git clone can be hard to work with

From: rsbecker@nexbridge.com <rsbecker@nexbridge.com>
Date: Jul 8, 2024, 15:02 UTC
Message-ID: <001201dad147$e9fdf9b0$bdf9ed10$@nexbridge.com>
In-Reply-To: <20240708143239.vq47dg7mgh33hykf@carbon>

On Monday, July 8, 2024 10:33 AM, Konstantin Khomoutov wrote:

Show 17 quoted lines

>On Mon, Jul 08, 2024 at 04:28:25AM +0200, ellie wrote:
>
>[...]
>> error: RPC failed; curl 92 HTTP/2 stream 5 was not closed cleanly:
>> CANCEL (err 8)
>[...]
>> It seems extremely unlikely to me to be possibly an ISP issue, for
>> which I already listed the reasons. An additional one is HTTPS
>> downloads from github outside of git, e.g. from zip archives, for way
>> larger files work fine as well.
>[...]
>
>What if you explicitly disable HTTP/2 when cloning?
>
>  git -c http.version=HTTP/1.1 clone ...
>
>should probably do this.

I can verify that this works in my environment.