I just got bit by this bug. Had to track down this report to get a solution, then had to figure out where the config file is stored on Windows to fix it. I would recommend that if read-only operations such as pull should fail due to SSH connection issues, then simply print a warning and attempt to fall back to HTTP.
I just got bit by this bug. Had to track down this report to get a solution, then had to figure out where the config file is stored on Windows to fix it. I would recommend that if read-only operations such as pull should fail due to SSH connection issues, then simply print a warning and attempt to fall back to HTTP.