Document Ruby bug #21195 in the README - #1189
Merged
Merged
Conversation
Ruby 3.3.0-3.3.7 and 3.4.0-3.4.2 can abort the process with "[BUG] rb_sys_fail_path_in(io_fillbuf, ...) - errno == 0" when a read using IO#timeout is interrupted by a signal. Dalli sets IO#timeout on its sockets, so users on those Rubies can hit it. Document the affected and fixed versions. Refs #1180. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Addresses the 5.x side of #1180. #1188 handles 4.x.
Ruby #21195: with
IO#timeoutset, a buffered read that a signal interrupts loses its error code, and Ruby aborts the whole process with[BUG] rb_sys_fail_path_in(io_fillbuf, ...) - errno == 0. Ruby code can't rescue it.5.x sets
IO#timeouton its sockets and requires Ruby 3.3+, so users on Ruby 3.3.0–3.3.7 or 3.4.0–3.4.2 can hit it. It's fixed in 3.3.8 and 3.4.3. CI isn't affected, because setup-ruby installs the latest patch releases.This adds a "Known Ruby issue" note to the README's Requirements section, with the affected and fixed versions, plus a changelog entry. Nothing under
lib/changes.🤖 Generated with Claude Code