Fix BufferedReader over a SocketIO to properly read the right amount#2409
Merged
Conversation
9e25621 to
231b5d5
Compare
231b5d5 to
235c384
Compare
youknowone
reviewed
Feb 3, 2021
03d0049 to
46ec578
Compare
46ec578 to
160505d
Compare
Member
Author
|
The re tests are fixed on master |
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
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.
This gets basic
requestsfunctionality working:I spent a lot of time debugging this, but I think the key thing that stopped it from hanging forever in
SocketIO.readintowas fixing_ioto useas_contiguousinstead ofobj_bytes, which wasn't taking the range of a memoryview into account, as well as changing a>to a>=in_io.