Issue #17470 has been updated by ioquatix (Samuel Williams).


> Timeout.timeout must be able to interrupt non-IO operations as well.

Actually, that's not necessarily true, even for the current implementation, see `getaddrinfo` for example.

----------------------------------------
Bug #17470: Introduce non-blocking `Timeout.timeout`
https://bugs.ruby-lang.org/issues/17470#change-89542

* Author: ioquatix (Samuel Williams)
* Status: Open
* Priority: Normal
* Backport: 2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: UNKNOWN
----------------------------------------
In this bug report, user complained that `Timeout.timeout` does not work correctly with scheduler: https://github.com/socketry/async-io/issues/43

We should introduce non-blocking timeout.

I propose the following:

```
rb_fiber_scheduler_with_timeout(VALUE scheduler, VALUE timeout, VALUE block)
```

We can directly modify `Timeout.timeout` to invoke this hook.



-- 
https://bugs.ruby-lang.org/

Unsubscribe: <mailto:ruby-core-request / ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>