-
Notifications
You must be signed in to change notification settings - Fork 380
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
request-server: don't return EOF if there is an unexpected error #392
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add a test. Thank you
Done, thank you |
io.EOF means no error so convert to ErrUnexpectedEOF if we detect a transfer error
Include this patch: pkg/sftp#393 to avoid request accumulation (no underlying fd) if we return an error. Before this patch the accumulated requests are released only when the client disconnects. We use our fork for now to include pkg/sftp#392 too
This way even if we do not read from this channel, there is not a blocked goroutine left hanging
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I cannot find anything else to even nitpick about. 😆
Thank you! |
These patches are now merged upstream: pkg/sftp#392 pkg/sftp#393
io.EOF means no error so convert to ErrUnexpectedEOF if we detect a transfer error