archive mirror
 help / color / mirror / Atom feed
From: Jeff King <>
To: "Kirill A. Shutemov" <>
	Andy Shevchenko <>,
	Konstantin Ryabitsev <>
Subject: Re: Problem accessing with git v2.33 plus gitproxy
Date: Mon, 30 Aug 2021 14:16:04 -0400	[thread overview]
Message-ID: <YS0gZNRqz72hs/> (raw)
In-Reply-To: <>

On Mon, Aug 30, 2021 at 07:11:49PM +0300, Kirill A. Shutemov wrote:

> 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 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 problem or git problem.
> Has anybody else stepped on the issue? Any clues?

I can't reproduce the problem here, using core.gitproxy with a script
identical to what you showed above. I tried both cloning, and fetching
via both git-fetch and git-fetch-pack.

Can you show us a more complete example? What does the command that
fails look like? What's the repo state before you run it? At what part
of the conversation does it fail (before a pack is sent, during, or

If you can reproduce it at will and it fails on 2.33 but not earlier,
then bisecting might be helpful.


  parent reply	other threads:[~2021-08-30 18:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-30 16:11 Problem accessing 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
2021-08-30 18:29   ` Andy Shevchenko
2021-08-30 18:30     ` Andy Shevchenko
2021-08-30 18:16 ` Jeff King [this message]
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YS0gZNRqz72hs/ \ \ \ \ \ \

* 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).