From: Jacob Keller Date: Tue, 31 Jan 2023 20:31:41 GMT Subject: Re: Bug: Cloning git repositories behind a proxy using the git:// protocol broken since 2.32 Message-ID: In-Reply-To: <339359ee8a228ea108109cf852bcb7e145807dcf.camel@siemens.com> On Tue, Jan 31, 2023 at 4:17 AM Florian Bezdeka wrote: > Thanks for the super fast response, highly appreciated! > > I was able to get it running by switching to ncat using the --no- > shutdown option, but I failed to bring back socat support so far. > > For me this is still a regression. We have to change our > infrastructure/environment because we have a new requirement > (independent handling of stdin/out) after updating git now. I would > expect some noise from the yocto/OE community in the future where oe- > git-proxy is heavily used. > > I guess proxy support was forgotten when the referenced change was > made. Any chance we can avoid closing stdout when running "in proxy > mode" to restore backward compatibility? > > Thanks a lot! I had this issue in the past and i got it working with socat using "-t 10". You need a timeout that is larger than the keep alive value of 5 seconds which is sent by the git protocol. Junio pointed out the excellent analysis from Peff regarding the situation and the fact that socat is wrong here. What value of -t did you try?