git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Taylor Blau <me@ttaylorr.com>
To: "Gibbons, Jason" <Jason.Gibbons@finastra.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: fetch-pack Unexpected disconnect issues in 2.47
Date: Tue, 15 Oct 2024 15:07:04 -0400	[thread overview]
Message-ID: <Zw69WPUT/9P327nx@nand.local> (raw)
In-Reply-To: <AS1PR08MB7514FB0AE229D34BFE66C4EF8A452@AS1PR08MB7514.eurprd08.prod.outlook.com>

On Tue, Oct 15, 2024 at 05:16:16AM +0000, Gibbons, Jason wrote:
> Hello
>
> Not sure if this has already been reported, but we have noticed that
> for a large github repository with lfs enabled, we are seeing the
> following errors on fetch:
>
> Connection to github.com closed by remote host.
>
> 03:42:26 fetch-pack: unexpected disconnect while reading sideband packet
> 03:42:26 fatal: early EOF
> 03:42:26 fatal: fetch-pack: invalid index-pack output
>
> When we revert the git client from 2.47 to 2.46 on the fetching host,
> the problem vanishes, and this is systematic both across CI build/test
> infrastructure and development PCs.
>
> For the moment we are just rolling back to 2.46 across our infra, but
> this can be only a short-term solution of course.

If you are using Git for Windows, I believe that there is a known issue
[1] which was patched in the MSYS2 runtime used by GfW [2].

It does not appear to be released as part of a tagged version of Git for
Windows yet, although from reading [1] it appears to be planned soon. In
the meantime, you should be able to work around the issue by using a
snapshot of Git for Windows.

Thanks,
Taylor

[1]: https://github.com/git-for-windows/git/issues/5199
[2]: https://github.com/git-for-windows/msys2-runtime/pull/75

      reply	other threads:[~2024-10-15 19:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-15  5:16 fetch-pack Unexpected disconnect issues in 2.47 Gibbons, Jason
2024-10-15 19:07 ` Taylor Blau [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=Zw69WPUT/9P327nx@nand.local \
    --to=me@ttaylorr.com \
    --cc=Jason.Gibbons@finastra.com \
    --cc=Johannes.Schindelin@gmx.de \
    --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).