From: <rsbecker@nexbridge.com>
To: "'Victor Porton'" <porton.victor@gmail.com>, <git@vger.kernel.org>
Subject: RE: Bug in Git
Date: Wed, 6 Mar 2024 19:22:45 -0500 [thread overview]
Message-ID: <092101da7025$97297b70$c57c7250$@nexbridge.com> (raw)
In-Reply-To: <0d741b90-8307-40cf-b0b3-163203651a57@gmail.com>
On Wednesday, March 6, 2024 6:52 PM, Victor Porton wrote:
>Recently updated Ubuntu 23.10:
>
>I tried it several times - the same result.
>
>$ git clone https://github.com/dfinity/motoko Cloning into 'motoko'...
>remote: Enumerating objects: 104759, done.
>remote: Counting objects: 100% (5702/5702), done.
>remote: Compressing objects: 100% (2333/2333), done.
>error: RPC failed; curl 92 HTTP/2 stream 5 was not closed cleanly:
>CANCEL (err 8)
>error: 1600 bytes of body are still expected
>fetch-pack: unexpected disconnect while reading sideband packet
>fatal: early EOF
>fatal: fetch-pack: invalid index-pack output
What version of git? Do you have a firewall or proxy between your machine and github? This works correctly on 2.42.1 with no proxy.
--Randall
prev parent reply other threads:[~2024-03-07 0:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-06 23:51 Bug in Git Victor Porton
2024-03-07 0:22 ` rsbecker [this message]
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='092101da7025$97297b70$c57c7250$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=git@vger.kernel.org \
--cc=porton.victor@gmail.com \
/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