Fix Buffering length edge cases - #1100
Open
OskarEichler wants to merge 1 commit into
Open
Conversation
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.
Summary
Align
OpenSSL::Bufferingread length handling with IO: reject negative read sizes, return an empty String forgets(..., 0), and stop filling once a positivegetslimit is available.Reproduction
The current implementation accepts negative lengths in
read,readpartial, andread_nonblock;gets(separator, 0)reads through separator/EOF and returns nil at EOF; and a positive limitedgetscontinues reading until separator/EOF after the requested bytes are buffered.Verification
-Werror; gem build/install and Songstats Rails/OpenSSL integration passNo public API is added; this corrects documented IO-compatible edge behavior.