-
Notifications
You must be signed in to change notification settings - Fork 770
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
Regression of 1545 #1993
Comments
I cannot repro this in the latest builds. But in addition, I feel the repro steps above are incorrect. As pointed out in the original issue (#1545 (comment)), you need to specify the command on the server that accepts the piped input. echo "test" | ssh win64bot3 pwsh
PS C:\ > "test"
test |
What does "latest builds" mean, what version exactly? The original issue was about how it should work without specifying the command. Specifying the command is a workaround. This is an important scenario for vscode's Remote-SSH extension. |
I was testing v8.9 and v9.1, but I see that the original fix went in v8.6 and it worked there. So this does look like a regression. |
Regression will be fixed on the next release (v9.1). |
Thank you! |
Do you know what the timeline is like for 9.1 reaching users via Windows Update? |
This was fixed with this PR (null ptr check): PowerShell/openssh-portable#616 |
Thanks, but do you know when it will reach Windows users? |
@roblourens It takes a number of months to ship the newer versions of OpenSSH to Windows. But you can get the beta version from the Releases page in this repo once we release it and install it using the instructions from our Wiki. |
I understand that it takes a number of months- the last time I reported a bug in this project, it took over a year. So I'm wondering whether you have a sense of what the timeline for the next release is like or is it to early to know? |
Unfortunately, we cannot comment on Windows release timelines. Our latest beta bits will always ship on GitHub and our in-box version be included in a Windows release at a later date. |
Prerequisites
Steps to reproduce
In #1545, an issue was fixed with piping into ssh without a command, eg
Downstream issue: microsoft/vscode-remote-release#7272 (comment)
I verified this as fixed in the 8.6 beta. In the issue above, it seems like the official 8.6 release actually has this issue. I haven't verified that myself. But I can verify it with the 8.9 beta from the releases page.
Expected behavior
It should echo "test"
Actual behavior
Now it fails with `client_loop: send disconnect: Broken pipe`
Error details
Environment data
The text was updated successfully, but these errors were encountered: