THRIFT-6133: Handle oversized Ruby memory-buffer reads - #3690
Merged
Conversation
Client: rb Co-Authored-By: OpenAI Codex (GPT-5.6) <codex@openai.com>
Member
Author
|
Fuzzer crash: |
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.
Native
MemoryBufferTransportconverted read sizes to a signed C integer before checking the bytes available. Positive Compact lengths aboveINT_MAXtherefore raisedRangeErrorinstead of reporting truncated input.The native implementation now preserves the requested Compact length through the availability check and returns
EOFErrorfor truncated oversizedreadandread_allcalls, matching pure Ruby behavior.[skip ci]anywhere in the commit message to free up build resources.