From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: git@vger.kernel.org, Jeff King <peff@peff.net>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
Greg Pflaum <greg.pflaum@pnp-hcl.com>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: Problem accessing git.kernel.org with git v2.33 plus gitproxy
Date: Mon, 30 Aug 2021 21:04:33 +0300 [thread overview]
Message-ID: <20210830180433.5rqqh7zsakbrfmrp@box> (raw)
In-Reply-To: <20210830161149.xggfosjthnjxcoxp@box.shutemov.name>
On Mon, Aug 30, 2021 at 07:11:50PM +0300, Kirill A. Shutemov wrote:
> Hi folks,
>
> I've stepped on a problem after upgrading git to v2.33.0. git fetch-pack
> fails with an error:
>
> fetch-pack: unexpected disconnect while reading sideband packet
>
> It only happens when I access git.kernel.org over git:// (github over
> git:// works fine) and if there's a gitproxy configured.
>
> For test I used a dummy gitproxy:
>
> #!/bin/sh -efu
> socat - "TCP:$1:$2"
>
> It is enough to trigger the issue.
>
> I'm not sure if it's kernel.org problem or git problem.
>
> Has anybody else stepped on the issue? Any clues?
I've bisected the issue to commit
ae1a7eefffe6 ("fetch-pack: signal v2 server that we are done making requests")
--
Kirill A. Shutemov
next prev parent reply other threads:[~2021-08-30 18:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-30 16:11 Problem accessing git.kernel.org with git v2.33 plus gitproxy Kirill A. Shutemov
2021-08-30 16:35 ` Konstantin Ryabitsev
2021-08-30 17:46 ` Pratyush Yadav
2021-08-30 18:04 ` Kirill A. Shutemov [this message]
2021-08-30 18:29 ` Andy Shevchenko
2021-08-30 18:30 ` Andy Shevchenko
2021-08-30 18:16 ` Jeff King
2021-08-30 18:28 ` Kirill A. Shutemov
2021-08-30 20:37 ` Jeff King
2021-08-30 22:42 ` Kirill A. Shutemov
2021-08-31 6:03 ` Jeff King
2021-08-31 8:46 ` Andy Shevchenko
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=20210830180433.5rqqh7zsakbrfmrp@box \
--to=kirill@shutemov.name \
--cc=andriy.shevchenko@linux.intel.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=greg.pflaum@pnp-hcl.com \
--cc=konstantin@linuxfoundation.org \
--cc=peff@peff.net \
/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).