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

From: Konstantin Khomoutov <kostix@bswap.ru>
Date: Jul 8, 2024, 15:44 UTC
Message-ID: <20240708154457.jpt2aa5orzxy6kqh@carbon>
In-Reply-To: <2e10070f-2720-4d70-aa15-d4c008cc57bf@horse64.org>

On Mon, Jul 08, 2024 at 05:14:33PM +0200, ellie wrote:

[...]

Show 9 quoted lines

> > > 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?

[...]

> Thanks for the idea! I tested it:
> 
> $  git -c http.version=HTTP/1.1 clone https://github.com/maliit/keyboard

Over there at SO people are trying all sorts of black magic to combat a problem which manifests itself in a way very similar to yours [1]. I'm not sure anything from there could be of help but maybe worth trying anyway as you can override any (or almost any) Git's configuration setting using that "-c" command-line option, so basically test round-trips should not be painstakingly long.

[...]

> fetch-pack: unexpected disconnect while reading sideband packet

[...]

> Sadly, it seems like the error is only slightly different.

I actually find it interesting that in each case a sideband packet is mentioned. But quite possibly it's a red herring anyway.

 1. https://stackoverflow.com/questions/66366582