git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Communication channel interruption

From
brian m. carlson <sandals@crustytoothpaste.net>
Date
Dec 14, 2023, 02:27 UTC
Message-ID
<ZXpoAVZ5BP9WqiZi@tapette.crustytoothpaste.net>
In-Reply-To
<71f2b28b-3e27-4773-8408-2f4c13757b73@gmail.com>
On 2023-12-13 at 09:54:30, Alexander Zhirov wrote:
Show 14 quoted lines
> When cloning a repository from GitHub, I have a channel break, although the
> connection is stable. What could be the problem?
> 
> # git clone https://github.com/Thinstation/thinstation.git
> Cloning into 'thinstation'...
> remote: Enumerating objects: 79839, done.
> remote: Counting objects: 100% (535/535), done.
> remote: Compressing objects: 100% (319/319), done.
> error: RPC failed; curl 92 HTTP/2 stream 5 was not closed cleanly: CANCEL
> (err 8)
> error: 7473 bytes of body are still expected
> fetch-pack: unexpected disconnect while reading sideband packet
> fatal: early EOF
> fatal: fetch-pack: invalid index-pack output

It would be helpful to know what version of Git, libcurl, and operating system you're using. This type of error is often caused by proxies, including non-default antivirus or firewall programs (very especially on Windows), TLS middleboxes, and monitoring software. If you have such software, it should be completely uninstalled and you should reboot, and usually that will fix the problem. (Simply disabling it often does not fix things.)

I should point out that while I'm aware that this does occur for many people, I have never, ever seen it when using GitHub, nor do I believe it is actually sent by GitHub servers. Thus, my experience leads me to believe the problem lies elsewhere. It is theoretically possible that libcurl or one of its dependencies has a bug in your version, but without more details, it's hard to tell.

As Junio suggested, you could try forcing HTTP/1.1 and see if that fixes the problem for you as well.

-- 
brian m. carlson (he/him or they/them)
Toronto, Ontario, CA
Previous: Junio C Hamano
Message 3 of 3 in “Communication channel interruption”
  1. Alexander ZhirovDec 13, 2023
  2. Junio C HamanoDec 13, 2023
  3. brian m. carlsonDec 14, 2023

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.