-
Notifications
You must be signed in to change notification settings - Fork 30.1k
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
[Remote-SSH Bug]: Error: AttachConsole failed, could not find pty on pty host #201029
Comments
Hmm, now the server refuses to connect with this error:
|
Does this still happen with the latest? |
Yes, I still see this (the original error about "AttachConsole failed"). Here's the relevant part of the log:
Version: 1.86.0-insider (user setup) |
I don't think this is really related to remote SSH, it looks like a native issue, perhaps a side-effect of recent version updates. |
Based on the logs might be a regression from microsoft/node-pty#510, should bump node-pty and check whether microsoft/node-pty#626 addresses the issue. |
This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines. Happy Coding! |
Hello! I disagree with the triage bot here :). |
@50Wliu I've been following several reports of this issue and this is the only report that the triage bot has yet to close automatically. It's like if they close their eyes and we go away, the problem is fixed! |
connect to remote windows server happens:
|
Is there an existing issue for this bug?
Required Troubleshooting Steps
remote.SSH.useLocalServer
settingConnect Locally
It connects successfully
->
No response
Expected Behavior
No error spew in the "Remote - SSH" log.
Steps To Reproduce
On connecting to a remote Windows host, I am now seeing console spew indicating that
getConsoleProcessList(shellPid)
fails with "Error: AttachConsole failed" and some "Could not find pty on pty host" errors.Remote-SSH Log
Remote-SSH Log
Anything else?
No response
The text was updated successfully, but these errors were encountered: