-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
2.16.1 (2) - Server 2008 - "error: cannot spawn sh: Function not implemented" #1475
Comments
Now working on Windwos 7 x64 error: cannot spawn git: Function not implemented |
Does this happen with every spawned process, e.g. also the editor when committing? If so, I suspect that the new code to inherit only the standard handles is the culprit (I had come to believe that it is using API introduced in Vista...) |
Yes, also when invoking the editor. Here: $ git commit -a |
The issues does not occur for me using commands like commit or status, only on commands that interact with remote repos, like fetch and push. |
"git status" works here as well. But "git commit" doesn't, and neither do Let me know if you need me to test more commands. |
Git CMD (Windows7 x64): git log -0 git stash list Git Bash does not have such problems. I downgraded git to v2.16.1.windows.1, and now it works as expected. |
I have the same problem with other commands:
The script (difftool.bash) is a simple wrapper to a sh file running some java program:
Also, I don't know if it is related - can't say for sure - the Windows shortcut "Git Bash" exit on start up (I assume there is some Running Gfw like this works: Info about my installation:
|
@dscho I can reproduce this on Windows While getting to the bottom of this issue, I'd recommend one of two workarounds for people who encounter this:
I'm also not aware if Git Bash has this issue. If you encounter a |
That's interesting... I specifically tested with Git CMD on Windows 10, and it seems to work. @shiftkey any chance you can instrument the code in |
@dscho i think this is a combination of Win7/Server 2008 (different kernel?) and Git CMD, so Win10 not showing the issue does make sense. I'll see if I can instrument things on Win7 and poke at the underlying error. |
The problem I reported, with $ git --version --build-options $ cat /etc/install-options.txt Maybe the triage which concluded my problem and this one is the same issue was wrong? Or maybe the fact that I don't use MinTTY (see above) is a factor? But otherwise, my problem definitely happens when invoking Git from Git Bash. Let me know how can I add more useful information. |
|
@shiftkey Hrmph. Yes, BinTray failed us. It is "rate limiting" Git for Windows. For some definition of "rate limiting". What it does in reality is to deny any service until their support gets in touch with me, which they claim might take a while because my free plan does not include any support option. So we're kinda stuck right now, between a rock and a hard place. |
Also Win7 SP1 can't work on to simple script:
but v2.16.1.0 work success. I downgarade v2.16.1(2) up to 2.16.1.0 .... |
@Eli-Zaretskii for practical purposes, you are using cmd.exe by using that choice. |
Ah, okay, thanks for clarifying. |
@dscho After |
@erw7 I spent all day today trying to figure this one out. Apparently, certain handles are inherited implicitly, and it has something to do with I found, for example, that restricting the list of handles to inherit to 0 handles worked. The I will still be trying to figure this one out until I understand every aspect of it, but I am tempted to simply disable the feature. Earlier today, I thought about simply disabling it based on the Windows version, but now I am thinking more about trying to detect this very error condition and just call Yes, it would exacerbate the locking issues we tried to fix, but honestly, a software that does not work is worse than a software that is really safe only on the newest Operating System. |
not working on windows 7 32bit.: |
@ulyanovvladimir are you trying to tell me that you tested with a Git for Windows that includes dc374ab? Because if you did test with such a version, I would be very interested in a lot more details. |
On Windows 7 and older, Git for Windows v2.16.1(2) was no longer able to spawn any processes (e.g. during fetch/clone). This regression [has been fixed](git-for-windows/git#1475). Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
1.16.1(2), 1.16.1(3) do not work. |
I can confirm that 1.16.1(3) still has issues |
@linquize @0x084E please open a fresh issue with full repro steps, so we can confirm whether it's the same problem or a different one |
I think it was already done, sorry for not looking before |
Thanks! I also test and Git dc364ab is working success. |
Surely you mean 2.16.1(2) and 2.16.1(3) ;-) But yes, I think #1481 is the ticket to discuss this, and I would love to get to the bottom of this as soon as possible. Every bit of help is greatly appreciated! |
Got the similar issue in Windows 10 , running bash terminal on Mobaxterm handle #0: 00000000000001d4 (type 3, handle info (1) 0 This is a bug; please report it at To suppress this warning, please set the environment variable
error: cannot spawn ssh: Function not implemented Setup
Details
** mobaxterm terminal **
** pull latest repo changes **
** error: cannot spawn ssh: Function not implemented |
Please upgrade, the problem will be magically gone, then. |
Issue persists in git version 2.36.0.windows.1 $ OS Details: Edition : Windows 10 Enterprise |
@ashokmagadum are you sure you get the exact same error? I am talking about this:
216 corresponds to |
I receive [" |
That's very different from the original report, which mentions ssh, not sh. |
This comment mentions SSH, but the original issue mentions SH
|
C:\xwiki\xwiki10\WEB-INF>git fetch
error: cannot spawn sh: Function not implemented
fatal: unable to fork
Verified the following:
Version:
git version 2.16.1.windows.2
cpu: x86_64
built from commit: e78e3c8
sizeof-long: 4
OS:
Server 2008 R2 Standard
Microsoft Windows [Version 6.1.7601]
Install Options:
Editor Option: VIM
Path Option: Cmd
SSH Option: OpenSSH
CURL Option: OpenSSL
CRLF Option: CRLFAlways
Bash Terminal Option: MinTTY
Performance Tweaks FSCache: Enabled
Use Credential Manager: Enabled
Enable Symlinks: Disabled
The text was updated successfully, but these errors were encountered: