Fix reading on a closed channel throw UnexpectedEof
error
#461
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Stop reading on a closed channel and stop it's keepalive timer.
This may cause an Error after a session closed:
I encountered in my workhorse project, and also find a related issue: #253
After a long trace in the source code, found that this is caused by
russh/russh/src/server/mod.rs
Line 903 in 89fed88
russh/russh/src/cipher/mod.rs
Line 254 in 89fed88
(insufficient data to be read)
this caused the "early eof" issue.
russh/russh/src/server/session.rs
Line 525 in 89fed88
this caused the "broken pipe" issue.