fetch-pack Unexpected disconnect issues in 2.47

fetch-pack Unexpected disconnect issues in 2.47

[Gibbons, Jason]

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.

Is there perhaps already a fix for this issue on the latest branch we could try out?
"FINASTRA" is the trade name of the FINASTRA group of companies. This email and any attachments have been scanned for known viruses using multiple scanners. This email message is intended for the named recipient only. It may be privileged and/or confidential. If you are not the named recipient of this email please notify us immediately and do not copy it or use it for any purpose, nor disclose its contents to any other person. This email does not constitute the commencement of legal relations between you and FINASTRA. Please refer to the executed contract between you and the relevant member of the FINASTRA group for the identity of the contracting party with which you are dealing.

Re: fetch-pack Unexpected disconnect issues in 2.47

[Taylor Blau]

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