git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Communication channel interruption
@ 2023-12-13  9:54 Alexander Zhirov
  2023-12-13 15:32 ` Junio C Hamano
  2023-12-14  2:27 ` brian m. carlson
  0 siblings, 2 replies; 3+ messages in thread
From: Alexander Zhirov @ 2023-12-13  9:54 UTC (permalink / raw)
  To: git

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Communication channel interruption
  2023-12-13  9:54 Communication channel interruption Alexander Zhirov
@ 2023-12-13 15:32 ` Junio C Hamano
  2023-12-14  2:27 ` brian m. carlson
  1 sibling, 0 replies; 3+ messages in thread
From: Junio C Hamano @ 2023-12-13 15:32 UTC (permalink / raw)
  To: Alexander Zhirov; +Cc: git

Alexander Zhirov <azhirov1991@gmail.com> 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?


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Communication channel interruption
  2023-12-13  9:54 Communication channel interruption Alexander Zhirov
  2023-12-13 15:32 ` Junio C Hamano
@ 2023-12-14  2:27 ` brian m. carlson
  1 sibling, 0 replies; 3+ messages in thread
From: brian m. carlson @ 2023-12-14  2:27 UTC (permalink / raw)
  To: Alexander Zhirov; +Cc: git

[-- Attachment #1: Type: text/plain, Size: 1726 bytes --]

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

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2023-12-14  2:27 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-12-13  9:54 Communication channel interruption Alexander Zhirov
2023-12-13 15:32 ` Junio C Hamano
2023-12-14  2:27 ` brian m. carlson

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).