incompatible with ractors

currently, timeout can't be used in ractors:

Ractor.new do
  Timeout.timeout(4) do
    sleep(5)
  end
end.take
# .rubies/ruby-3.3.0/lib/ruby/3.3.0/timeout.rb:129:in `ensure_timeout_thread_created': can not access non-shareable objects in # # constant Timeout::TIMEOUT_THREAD_MUTEX by non-main ractor. (Ractor::IsolationError)
#         from .rubies/ruby-3.3.0/lib/ruby/3.3.0/timeout.rb:178:in `timeout'
#         from (irb):8:in `block in <top (required)>'

Lots of downstream dependencies rely on timeout, and this makes them unusable under ractors.

I think Thread in general is considered incompatible with Ractor (it breaks the programming model and there are several bugs with Ractor & threads), and so Timeout (which needs threads) is incompatible with Ractor.

Also: https://bugs.ruby-lang.org/issues/18139#note-2

I wouldn't go so far. If timeout would use ractor-local thread/queue/cond/mutex, it'd work. A completely alternative ractor-friendly implementation could also be an option (although I can't think of one). Was just pointing out that, the way it's implemented, it's unusable.

@jsvd

@jsvd I don't consider this related, so that would be best as its own discussion or issue.

@eregon

@eregon fair enough, I moved the comment to a new issue #58

@ko1

Fixed in #75 (thanks @ko1!)

Navigation Menu

Repository navigation

incompatible with ractors #53

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

incompatible with ractors #53

Description

Activity

eregon commented on Oct 29, 2024

HoneyryderChuck commented on Oct 29, 2024

jsvd commented on Jan 17, 2025

eregon commented on Jan 17, 2025

jsvd commented on Jan 17, 2025

eregon commented on Dec 5, 2025

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions