Don't crash when a message is split in the middle of the payload length field. #22
Conversation
This file contains 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
Pull Request Test Coverage Report for Build c06e81a81b9d62a18bb3c48fe8e4af1cf5dfb4e8-PR-22
💛 - Coveralls |
the-mikedavis
approved these changes
Sep 18, 2022
|
Thanks! I released this as v1.0.1 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Today, when a packet happens to be split in the middle of the frame length, the
:malformed_payload_lengtherror will be returned. However, we should just buffer it so we can finish processing it when the next message arrives.Example packet ending:
"...}\n\x82~\x01"Error:
{:malformed_payload_length, <<252, 1::size(7)>>}