Fix MessageUnapcker.prepareNumberBuffer#363
Merged
Conversation
prepareNumberBuffer was assuming that a buffer chunk includes at least `readLength` bytes of data. Maximum size of `readLength` is 8. Therefore, a problem could always happen if MessageBufferInput returns buffer chunks smaller than 8 bytes.
…uffer-boundary-test
Member
|
Nice catch. I added test cases to reproduce this issue. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
prepareNumberBuffer was assuming that a buffer chunk includes at least
readLengthbytes of data. Maximum size ofreadLengthis 8.Therefore, a problem could always happen if MessageBufferInput returns
buffer chunks smaller than 8 bytes.