Closed mrowell closed 2 years ago
While -CHECK_HOME
would stop the connection process from failing if the shell command used to find the home directory failed or if the given home directory wasn't an accessible directory, it wouldn't actually account for the creation of the shell failing.
This should now be fixed (c7f1261), which you can test in the latest build here. Might end up creating a release for that today (with or without other commits), but still working on something right now.
I've tested the build you created and that works without issue.
Thank you so very much for promptly fixing the problem and for such a useful VSCode extension.
It's now released in v1.21.0 of the extension.
If you're not using VS Code but an IDE that uses OpenVSX, you might have to manually update, due to an issue in OpenVSX.
Since upgrading to version 1.21.0 we receive an
Error while connecting to SSH FS ***hostname***: Unable to exec
error and the connections fails.Reverting to version 1.20.2 and the connection succeeds without issue.
The server is SFTP only (ie no SSH). The client is macOS 10.15.1, VS Code 1.58.2.
I also tried with the
-CHECK_HOME
flag set as the server does present the User's home directory. I received the same error.Here are the DEBUG_SSH2 logs:
If I can do any further testing to assist, please don't hesitate to ask. Thanks, Marcus.