# Communication channel interruption 3 messages from 2023-12-13 to 2023-12-14. Participants: Alexander Zhirov, Junio C Hamano, brian m. carlson. Thread: https://gitlist.dev/t/60610 ## Alexander Zhirov, 2023-12-13 09:54 Subject: Communication channel interruption Message-ID: <71f2b28b-3e27-4773-8408-2f4c13757b73@gmail.com> URL: https://gitlist.dev/e/71f2b28b-3e27-4773-8408-2f4c13757b73%40gmail.com ``` 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 ``` ## Junio C Hamano, 2023-12-13 15:32 Subject: Re: Communication channel interruption Message-ID: URL: https://gitlist.dev/e/xmqqcyvanmn7.fsf%40gitster.g In-Reply-To: <71f2b28b-3e27-4773-8408-2f4c13757b73@gmail.com> ``` Alexander Zhirov writes: > 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 A guess in the dark without knowing Git version or platform on which you are seeing this symptom, but it would help to read "What does http.postBuffer really do?" in $ git help faq and then to ask Google about "RPC failed; curl 92", which would show mainly two suggestions from various places. Perhaps $ git -c http.version=HTTP/1.1 clone https://github.com/Thinstation/thinstation.git may help? ``` ## brian m. carlson, 2023-12-14 02:27 Subject: Re: Communication channel interruption Message-ID: URL: https://gitlist.dev/e/ZXpoAVZ5BP9WqiZi%40tapette.crustytoothpaste.net In-Reply-To: <71f2b28b-3e27-4773-8408-2f4c13757b73@gmail.com> ``` On 2023-12-13 at 09:54:30, Alexander Zhirov wrote: > 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 ```