From: Bagas Sanjaya <bagasdotme@gmail.com>
Date: Sat, 23 Oct 2021 03:58:11 GMT
Subject: Re: Error in 'git clone' via SSH in v2.33.0 (related to commit ae1a7ee)
Message-ID: <b802e803-520d-49f5-a845-8e3c94f1c0ee@gmail.com>
In-Reply-To: <CAN2Gq0de1tpiLNcQqoZmgAu=kuOXxEmAtziWM7OJtGPGhLneYQ@mail.gmail.com>

On 22/10/21 21.26, Philipp Eib wrote:
> Hi,
> 
> Using git-for-windows, I noticed that an SSH git clone of an internal
> repo broke for me in git v2.33.0
> The exact error is:
> 
> fetch-pack: unexpected disconnect while reading sideband packet/s
> fatal: early EOF
> fatal: fetch-pack: invalid index-pack
> 
> Cloning via HTTPS continued to work.
> It was also repository-specific as cloning other repositories from the
> same (Gitlab) instance via SSH was working fine.
> 
> Together with the maintainer we traced the problem back to git commit
> ae1a7ee (https://github.com/git/git/commit/ae1a7eefffe60425e6bf6a2065e042ae051cfb6c).
> Reverting this commit and rebuilding fixed the issue within git-for-windows.
> (You can read the full conversation here:
> https://github.com/git-for-windows/git/issues/3444)
> 
> Unfortunately I cannot give a reproducible example as the internal
> repository cannot be shared.
> I have also not tested on linux.
> 
> Regards,
> Philipp
> 

I've tried to reproduce this issue on Ubuntu 20.04, using the same Git 
version. I cloned from a Git server hosted on my own computer under LXD, 
and the operation worked as expected.

Try adding GIT_TRACE_PACKET=true when attempting to clone the 
problematic repo.

-- 
An old man doll... just what I always wanted! - Clara