git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Alexander Zhirov <azhirov1991@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Communication channel interruption
Date: Wed, 13 Dec 2023 07:32:44 -0800	[thread overview]
Message-ID: <xmqqcyvanmn7.fsf@gitster.g> (raw)
In-Reply-To: <71f2b28b-3e27-4773-8408-2f4c13757b73@gmail.com> (Alexander Zhirov's message of "Wed, 13 Dec 2023 12:54:30 +0300")

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?


  reply	other threads:[~2023-12-13 15:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-13  9:54 Communication channel interruption Alexander Zhirov
2023-12-13 15:32 ` Junio C Hamano [this message]
2023-12-14  2:27 ` brian m. carlson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqcyvanmn7.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=azhirov1991@gmail.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).