Skip to content

Document Ruby bug #21195 and drop Ruby 3.2 from CI #1188

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
petergoldstein merged 2 commits into from
Oct 4, 2026
Merged

Document Ruby bug #21195 and drop Ruby 3.2 from CI #1188

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a10778e
Document Ruby bug #21195 and drop Ruby 3.2 from CI
petergoldstein Oct 4, 2026
366aae3
Add PR number to changelog entries
petergoldstein Oct 4, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 0 additions & 1 deletion .github/workflows/tests.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,6 @@ jobs:
- '4.0'
- '3.4'
- '3.3'
- '3.2'
- '3.1'
- jruby-10
- truffleruby
Expand Down
7 changes: 7 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,8 +4,15 @@ Dalli Changelog
Unreleased
==========

Notes:

- Document [Ruby bug 21195](https://bugs.ruby-lang.org/issues/21195), a VM crash (`[BUG] rb_sys_fail_path_in(io_fillbuf, ...) - errno == 0`) when a socket read using `IO#timeout` is interrupted by a signal, in the README (#1188)
- Affects Ruby 3.2.x, 3.3.0–3.3.7 and 3.4.0–3.4.2. Fixed in 3.3.8 and 3.4.3; Ruby 3.2 reached end of life without the fix
- Ruby 3.1 doesn't use `IO#timeout` and isn't affected

Development:

- Drop Ruby 3.2 from the CI matrix, since that bug intermittently crashed its test runs (#1188)
- Fix three flaky tests: the `KeyManager` namespace key-length test, the Rack session freshness test, and `MemcachedManager`'s start and stop handling (backport of #1141, #1182)
- Fix flaky failover tests: move their ports out of Linux's ephemeral port range, and wait for memcached to accept connections after starting it (backport of #1184)

Expand Down
12 changes: 12 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,6 +20,18 @@ The name is a variant of Salvador Dali for his famous painting [The Persistence
* Ruby 3.1 or later
* memcached 1.4 or later (1.6+ recommended for meta protocol support)

### Known Ruby issue: crash on an interrupted socket read

On Ruby 3.2 and later, Dalli sets socket timeouts with `IO#timeout`. Ruby 3.2.x, 3.3.0–3.3.7 and 3.4.0–3.4.2 have a bug ([Ruby #21195](https://bugs.ruby-lang.org/issues/21195)) where a timed read interrupted by a signal aborts the whole process:

```
[BUG] rb_sys_fail_path_in(io_fillbuf, fd:N ) - errno == 0
```

The crash is inside Ruby itself, so it can't be rescued. It was fixed in Ruby 3.3.8 and 3.4.3. Ruby 3.2 reached end of life without the fix. If you see this crash, upgrade to Ruby 3.3.8+ or 3.4.3+. Ruby 3.1 doesn't use `IO#timeout` and isn't affected.

Ruby 3.2 is no longer part of this branch's CI matrix for the same reason.

## Protocol Options

Dalli supports two protocols for communicating with memcached:
Expand Down
Loading