-
Notifications
You must be signed in to change notification settings - Fork 602
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
Defect introduced in code cleanup commit? #306
Comments
Can you create a unit test that simulates this? |
I'm super-busy at the moment, but I will give it a shot if you'll point me to an existing unit test that attempts to execute any command over an exec or shell channel. If you can't, it'll just take me longer to get around to it. |
Hi David, else do you have some logging and string sizing info for me?
Op 9 mrt. 2017 6:37 p.m. schreef "David Solin" <[email protected]>:
… I'm super-busy at the moment, but I will give it a shot if you'll point me
to an existing unit test that attempts to execute any command over an exec
or shell channel.
If you can't, it'll just take me longer to get around to it.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#306 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAHLowcb-STGA5ryiIsVMuvBfb0Qchqqks5rkDjGgaJpZM4MXcmc>
.
|
Hi Jeroen, sorry I never managed to get that unit test working. I just tried this update and it appears fixed to me. Thanks! |
No problem, the keen eyes of @dkocher found the issue ;) |
I'm seeing the following exception sending really long strings down a ChannelOutputString, which I don't see when using a previous build:
I looked cursorily and didn't see a problem, but I suspect this might have been broken in commit 636f896.
The text was updated successfully, but these errors were encountered: