From: Evan Miller <emmiller@gmail.com>
To: "brian m. carlson" <sandals@crustytoothpaste.net>
Cc: git@vger.kernel.org
Subject: Re: Exit code 255 after large clone (32-bit PowerPC)
Date: Mon, 26 Jul 2021 18:50:39 -0400 [thread overview]
Message-ID: <E5CF61E9-8817-4FB9-B604-C97BF3DFE8B4@gmail.com> (raw)
In-Reply-To: <YP8ykvsZie4mPE5o@camp.crustytoothpaste.net>
> On Jul 26, 2021, at 18:09, brian m. carlson <sandals@crustytoothpaste.net> wrote:
>
> On 2021-07-26 at 17:54:07, Evan Miller wrote:
>> What did you do before the bug happened? (Steps to reproduce your issue)
>>
>> $ git clone -v git@github.com:macports/macports-ports.git
>> Cloning into 'macports-ports'...
>> remote: Enumerating objects: 1223319, done.
>> remote: Counting objects: 100% (685/685), done.
>> remote: Compressing objects: 100% (341/341), done.
>> remote: Total 1223319 (delta 289), reused 608 (delta 252), pack-reused 1222634
>> Receiving objects: 100% (1223319/1223319), 244.46 MiB | 1.09 MiB/s, done.
>> Connection to github.com closed by remote host.
>
> This message is the relevant detail here. This means that the
> connection was reset, which could be due to the remote host (GitHub),
> but is more likely due to a network issue of some sort. You'll have to
> do normal network troubleshooting to see why that might be.
>
> It could very well be related to the fact that you're running a nearly
> 14-year old operating system, but I just can't say for certain. It's
> not a bug in Git, however.
>
> Even if the data is otherwise transferred successfully, Git will exit
> unsuccessfully if this happens, and that will result in your data not
> being checked out.
Thanks. The issue happens repeatedly on this machine, which is connected via Ethernet to residential fiber. I am doubtful of a generic network issue, but I will try an updated SSH client. (The issue does not happen over HTTPS.)
In any event, it would be good to have a more informative error message in this kind of situation. It is surprising that the data transfer is successful, and the Deltas are computed, but the overall checkout fails.
Evan
> --
> brian m. carlson (he/him or they/them)
> Toronto, Ontario, CA
next prev parent reply other threads:[~2021-07-26 22:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-26 17:54 Exit code 255 after large clone (32-bit PowerPC) Evan Miller
2021-07-26 22:09 ` brian m. carlson
2021-07-26 22:50 ` Evan Miller [this message]
2021-07-27 0:51 ` Ævar Arnfjörð Bjarmason
2021-07-27 1:37 ` brian m. carlson
2021-07-27 2:20 ` Junio C Hamano
2021-07-27 3:05 ` Evan Miller
2021-07-27 12:44 ` Jeff King
2021-07-27 2:08 ` Evan Miller
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=E5CF61E9-8817-4FB9-B604-C97BF3DFE8B4@gmail.com \
--to=emmiller@gmail.com \
--cc=git@vger.kernel.org \
--cc=sandals@crustytoothpaste.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.