Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Git protocol hangs indefinitely. #89

Closed
ghost opened this Issue Jan 4, 2013 · 16 comments

Comments

Projects
None yet
7 participants
@ghost

ghost commented Jan 4, 2013

I've just started building a CI server with Window Server 2012 and hit a issue where git-push hangs indefinitely.

Did some research and found this but it appears to have been forgotten about; there's nothing on here either about it being a problem.

This is still occurring with 1.8.0.msysgit.0.

The same problem appears in case the git deamon runs on Linux and you try to push from Windows (1.8.3.msysgit.0). Tried couple of "wanna be" workarounds but none seemed to work.

@ghost

ghost commented Aug 20, 2013

I'd forgotten about this! I just gave up. Also, looks like I wasn't able to communicate 8 months ago too.

For clarification:

  • I was pushing to Windows Server 2012, from Windows 7,
  • I was using version 1.8.0.msysgit.0,
  • I still haven't been able to get git-push to work successfully.

From @temistokles reply it appears that the issue is with git-push being unable to either connect or bail out.

I remember reading the server log and seeing no connection being made.

Owner

dscho commented Sep 5, 2013

I fear that the only way this could be resolved is to debug by using the development environment of Git for Windows and litter the code with debug messages to figure out where it gets stuck and why. This is only possible, of course, in a setup that shows that problem (which I do not have).

Contributor

t-b commented Sep 6, 2013

A step-by-step guide to reproduce it is really necessary. I've never hit that issue with my setup (client: current git for windows, server debian squeeze with ssh access only).

Owner

dscho commented Dec 30, 2013

Okay, four months is really long enough a wait for people who were willing to fix other people's problems.

@dscho dscho closed this Dec 30, 2013

Contributor

t-b commented Oct 6, 2014

@socantre If that would be the OPs problem, there is a official workaround since msysgit/git@ea8c6fc.

socantre commented Oct 6, 2014

@t-b Yeah, one of my links points to a mailing list that discusses that patch. It didn't work in 1.9.2 and I came here to see if it was safe to update (so I wouldn't have to apply a binary patch or build from source yet again) and saw this issued simply closed. I hadn't realized it had actually gone in, so you've prompted me to upgrade to 1.9.4 where the issue is finally fixed via that workaround. Thanks.

Contributor

t-b commented Oct 7, 2014

@socantre The workaround I mentioned is in git since Git-1.9.4-preview20140611.

jtgans commented Jun 21, 2015

Wait, why is this closed? I just ran into this recently on 1.9.5.msysgit.1 and it /still hangs/ without the workaround flag turned on.

Can we just default this flag to true in the msysgit builds?

Owner

dscho commented Jun 21, 2015

Wait, why is this closed?

Hehe... the answer is in this ticket: #89 (comment)

Are you the person driving the resolution of this issue forward? If so, I will gladly reopen (although I will insist to focus on Git for Windows 2.x, which already saw the 3rd release candidate.

jtgans commented Jun 21, 2015

Is this also a problem for GfW? If so, I'd be happy to send along a patch to enable the workaround by default.

Owner

dscho commented Jun 21, 2015

Is this also a problem for GfW?

I do not know; I never experienced the problem myself, so I cannot test.

Seeing what looks to be the same problem in 2.8.1.windows.1

Owner

dscho commented Apr 16, 2016

@johnnyb johnnyb referenced this issue in git-for-windows/git Oct 5, 2016

Open

Git Push Not working for git:// protocol servers #907

1 of 1 task complete

johnnyb commented Oct 5, 2016

I just wanted to leave a comment for those finding this page that the way to work around it is by running this command:

git config --global sendpack.sideband false

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment