[Windows] bash: /dev/tty: No such device or address

[koistya]

Repo#remote_fetch(name, callback)

Error: Command failed: C:\Windows\system32\cmd.exe /s /c "git fetch  staging"
bash: /dev/tty: No such device or address
error: failed to execute prompt script (exit code 1)
fatal: could not read Username for 'https://<site>.scm.azurewebsites.net': No error

Running the same command from the console works fine.

C:\Windows\system32\cmd.exe /s /c "git fetch  staging"

Windows 8.1 x64, Git 2.5.0

[Smolkis]

I have had similar problems with the same error message, and I managed to get around it be installing an old version of git

[notatestuser]

I don't know of a solution to this. Any Windows users able to chime in?

[Drumsticks]

I'm having this very issue right now. It was working after getting everything set up with up with Bitbucket and Jenkins. Literally the next day, I come in to test again and I receive this error in the Jenkins Build Log.

This is the error that I receive when attempting an origin pull:

• I do actually have a real username in place of "username".

git pull origin master
bash: /dev/tty: No such device or address
error: failed to execute prompt script (exit code 1)
fatal: could not read Password for 'https://"username"@bitbucket.org': Invalid argument

If there is a solution, I would love to know. Thank you.

[Drumsticks]

After troubleshooting my issue. It was that the command / git bash terminals did not have the password saved for Open SSH. When Jenkins was attempting to run the scripts in the terminal, it was throwing the error because it was unable to get past the invisible password prompt since the script is automatically ran. When I attempted an origin pull manually in either terminal, I received the password prompt and entered the password.

I then close the terminals, re-opened the terminals to make sure the password was not temporarily stored in the previous terminal session and the password kept as I was not prompted again.

I tested Jenkins by building again and everything worked perfectly.

I hope this may help anyone coming here.

[eliranmal]

this issue stems from an issue on git-for-windows