-
Notifications
You must be signed in to change notification settings - Fork 357
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
[SSHD-849] Using a ClientChannelPendingMessagesQueue to regulate messages order while forwarding channel is being set up #72
Conversation
The code can also be checked out and tested from https://github.com/lgoldstein/mina-sshd/tree/SSHD-849. |
We have tested you modifications, but we have found some problems, I thinks related to |
Good news - will await your input |
e429576
to
0315a68
Compare
Hi Lyor, |
There are quite a few issues with this code - however, I think you are on to something with the usage of the extra future (the completion one). I have made the changes based on your idea into my original code and pushed it into the same branch (https://github.com/lgoldstein/mina-sshd/tree/SSHD-849) + PR. Can you review + test it an see ? |
758b2bb
to
6f68fb3
Compare
…ages order while forwarding channel is being set up
Hi,
your modifications seems to be good. We're still testing with previous one
since we're now trying to overcome problems with SSH_MSG_CHANNEL_WINDOW_ADJUST
management that, since it's blocking, it's forcing us to use a thread poll
equal to max level of concurrent channels.
We'll test your version of the modification in the next days and give you a
feedback.
Il giorno mar 23 ott 2018 alle ore 17:37 Lyor Goldstein <
notifications@github.com> ha scritto:
… There are quite a few issues with this code - however, I think you are on
to something with the usage of the extra future (the completion one). I
have made the changes based on your idea into my original code and pushed
it into the same branch (
https://github.com/lgoldstein/mina-sshd/tree/SSHD-849) + PR. Can you
review + test it an see ?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#72 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ASs-3VyQSJlliwPElJcpBBBTabAQNd-fks5unze1gaJpZM4XtlUs>
.
|
Great - hope you can overcome the |
No description provided.