-
Notifications
You must be signed in to change notification settings - Fork 31
Use sync socket write to ensure that full message is written #39
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
Closed
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
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 believe the cause of truncated messages is likely caused by our failure to check the return value of
IO#syswrite
; if a payload is partially written at this level, we make no attempt to continue writing from where we left off.We can fix that by performing a byteslice and repeating the
IO#syswrite
call with the remainder until the remaining payload is empty:Separately, the code that this removes gives us an opportunity to have an
EOFError
be raised before we send data if the remote end closes the socket on us, while the replacement will raise aSystemCallError
whenIO#syswrite
is sent to a closed socket. I have not thought through all of the ramifications of changing the error being raised.I think there is definitely a bug in the implementation, in which a socket that is readable (e.g., the remote end has sent bytes that are not
EOF
) and not writable (e.g., has a zero window) would cause thepayload
to be dropped instead of written.I believe this secondary issue can be solved by retrying the
IO::select
until we have a writableclient_socket
:There may be dragons here, if the socket never becomes writable or readable with an
EOF
, but these dragons also exist in the current implementation and are not a new addition.