Skip to content
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

SshCommand OutputStream has no way to directly set BlockLastReadBuffer #142

Closed
hifi opened this issue Dec 27, 2016 · 1 comment · Fixed by #1399
Closed

SshCommand OutputStream has no way to directly set BlockLastReadBuffer #142

hifi opened this issue Dec 27, 2016 · 1 comment · Fixed by #1399

Comments

@hifi
Copy link
Contributor

hifi commented Dec 27, 2016

When reading the stdout of a process executed through SshCommand the output stream will throw an exception if you read beyond what's available in the buffer and it seems to be by design.

Although in my opinion this is the wrong default, there's no direct way to change the property at runtime as the exposed interface is the standard Stream.

Could the default be changed to more sensible blocking behavior or there be a public method/property that can be used to change it at runtime?

@hifi
Copy link
Contributor Author

hifi commented Dec 29, 2016

PR #144 has a big rewrite that fixes this as well by removing this option completely.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant