Re: possible race condition (fetch-pack: unexpected disconnect while reading sideband packet)

From: brian m. carlson <sandals@crustytoothpaste.net>
Date: Apr 16, 2021, 00:04 UTC
Message-ID: <YHjUd67KujPCl1U9@camp.crustytoothpaste.net>
In-Reply-To: <YHf5bkiE7SVPTBvU@coredump.intra.peff.net>

On 2021-04-15 at 08:29:34, Jeff King wrote:

Show 16 quoted lines

> On Wed, Apr 14, 2021 at 10:12:44AM +0000, Simon, Martin (Digiteq Automotive) wrote:
> 
> > Actual result (when failed):
> > Cloning into 'local-repo-name'...
> > remote: Enumerating objects: 237, done.
> > remote: Counting objects: 100% (237/237), done.
> > remote: Compressing objects: 100% (129/129), done.
> > fetch-pack: unexpected disconnect while reading sideband packet
> > fatal: early EOF
> > fatal: fetch-pack: invalid index-pack output
> 
> This could be many things. A bug or race on the client side is possible,
> but it could also be that the network session really _is_ being
> disconnected. This could be something in the network stack itself
> terminating the connection, or it could be a bug or other error on the
> server.

I'll point out that this kind of occurrence also happens if folks are using proxies or TLS middleboxes, as well as some antivirus and firewall programs on Windows (which often end up being well-hidden proxies due to their configuration, unfortunately). That usually only applies to HTTPS, so oftentimes switching to SSH, as Peff suggested, may be a good choice.

You can also try running the operation under WSL 2, which generally is not subject to most of those programs and mostly handles its own networking, to see if it is one of those programs or if there's a more general network- or protocol-specific problem. That will at least give you more information about the nature of what's going on and help you troubleshoot further.

-- 
brian m. carlson (he/him or they/them)
Houston, Texas, US