threads / discuss / 56695

Commit ae1a7eefff may have broken git behind a firewall

Subject: Commit ae1a7eefff may have broken git behind a firewall

## tl;dr

3 messages between Oct 12, 2021 and Oct 12, 2021.

replies: 2people: 2as markdown or json

H.J. Lu· Oct 12, 2021, 21:03 UTC · lore

https://github.com/git/git/commit/ae1a7eefff

may have broken git behind a firewall:

https://bugzilla.redhat.com/show_bug.cgi?id=2013288

I am behind a firewall and using gitproxy:

exec socat - socks4:proxy-server-name:$1:$2

I got

$ git clone git://gcc.gnu.org/git/gcc.git Cloning into 'gcc'... fetch-pack: unexpected disconnect while reading sideband packet fatal: early EOF fatal: fetch-pack: invalid index-pack output $

Both

$ git clone --depth 1 git://gcc.gnu.org/git/gcc.git

and

$ git clone https://gcc.gnu.org/git/gcc.git

work.

$ git -c protocol.version=1 clone git://gcc.gnu.org/git/gcc.git

also works.

-- 
H.J.

Jeff King· Oct 12, 2021, 21:17 UTC · re: H.J. Lu · lore

Re: Commit ae1a7eefff may have broken git behind a firewall

On Tue, Oct 12, 2021 at 02:03:39PM -0700, H.J. Lu wrote:

Show 9 quoted lines

> https://github.com/git/git/commit/ae1a7eefff
> 
> may have broken git behind a firewall:
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=2013288
> 
> I am behind a firewall and using gitproxy:
> 
> exec socat - socks4:proxy-server-name:$1:$2

It's not the firewall; it's socat not handling half-duplex shutdown very well (though you are right that it is related to the commit you found; that's when Git started closing the write pipe when it's done writing).

More discussion in this thread:

  https://lore.kernel.org/git/YS1Bni+QuZBOgkUI@coredump.intra.peff.net/

(the short answer is: use "socat -t 10").

-Peff

H.J. Lu· Oct 12, 2021, 21:41 UTC · re: Jeff King · lore

Re: Commit ae1a7eefff may have broken git behind a firewall

On Tue, Oct 12, 2021 at 2:17 PM Jeff King <peff@peff.net> wrote:

Show 24 quoted lines

>
> On Tue, Oct 12, 2021 at 02:03:39PM -0700, H.J. Lu wrote:
>
> > https://github.com/git/git/commit/ae1a7eefff
> >
> > may have broken git behind a firewall:
> >
> > https://bugzilla.redhat.com/show_bug.cgi?id=2013288
> >
> > I am behind a firewall and using gitproxy:
> >
> > exec socat - socks4:proxy-server-name:$1:$2
>
> It's not the firewall; it's socat not handling half-duplex shutdown very
> well (though you are right that it is related to the commit you found;
> that's when Git started closing the write pipe when it's done writing).
>
> More discussion in this thread:
>
>   https://lore.kernel.org/git/YS1Bni+QuZBOgkUI@coredump.intra.peff.net/
>
> (the short answer is: use "socat -t 10").
>
> -Peff

Yes, "socat -t 10" works.

Thanks.

-- 
H.J.