New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Git daemon broken on windows (WSAStartup) #1952
Comments
Could you please test the latest snapshot from https://wingit.blob.core.windows.net/files/index.html? I think this bug has been fixed in the meantime. BTW v2.19.2 has been bumped down to "pre-release" status in part because of that bug. |
https://git-scm.com/download/win still serves this as download. |
Steps taken:
|
Wonderful. I'll close it here, then. FWIW my current plan is to not release any v2.19.2(2), but to release Git for Windows v2.20.0 short after Git v2.20.0 is released (expected Dec 2nd). |
Thanks for the quick response! |
This bug also prevents cloning remote repositories with git:// URLs, for example: 'git clone git://git.apache.org/commons-compress.git'. The error message is similar and contains: "(port 9418) (Either the application has not called WSAStartup, or WSAStartup failed. )". I've switched from 2.19.2.windows.1 into 2.20.0.rc2.windows.1 (both 64 bit) and now I'm able to clone remote repositories with git:// URLs. |
Still experiencing the error in git 2.21.0.windows1 with gitkraken 5.0.4 on Windows 10 1809. |
Are you sure that the version that is actually used is v2.21.0? There are two Git versions involved, after all. The client and the server. |
Also: did you try this without gitkraken in the middle? |
For the server side, I am working on github and the problem only occurs with Gitkraken in between. But after all Gitkraken is just a drilldown, right? So this is weird. |
I have no idea what GitKraken uses. |
I'm still having this issue with
Only when pushing to gitlab. Github works fine. If i try without gitkraken in the middle it also works. Switching branches works in girkraken Maybe gitkraken uses the faulty git version under the hood? |
Maybe. Do you have any Git Kraken contact you could ask? |
no. They only accept support requests from PRO users. From this article it seems like they use the system's git version though: it's also strange that it only fails for one provider: Gitlab and not for Github. So you would think it has to do with how Gitlab works rather than the git version. Or the combination of gitkraken with gitlab. for reference, this is the error popup: These are some of the logs in the gitkraken log viewer:
and the application log:
|
@bertyhell maybe open a separate ticket, then, just to track your issue (which seems to be totally unrelated to a broken |
Fair enough. I'll see if i can contact Gitkraken first somehow. |
For future reference, here's how to enable the advanced logs for gitkraken:
I could not reproduce the issue anymore though. |
Setup
defaults?
to the issue you're seeing?
Details
Minimal, Complete, and Verifiable example
this will help us understand the issue.
Not sure if this is relevant, but in case it might be:
The daemon is not used to serve one repository, but instead it serves all repositories in the selected folder.
What did you expect to occur after running these commands?
What actually happened instead?
Free-handed translation:
URL to that repository to help us with testing?
update:
Downgrading to
v2.19.1
fixes the issue for me.ps: Nice bug reporting template 👍
The text was updated successfully, but these errors were encountered: