ruby.git/lib/timeout.rb, branch v3_2_11

[ruby/timeout] Bump version to 0.3.1

2022-12-05T08:13:18+00:00

https://github.com/ruby/timeout/commit/4941e8c871

[ruby/timeout] Explicit add the timeout thread to default ThreadGroup

2022-09-27T16:59:35+00:00

Otherwise the timeout thread would be added to the ThreadGroup of the thread that makes the first call to Timeout.timeout .

Fixes bug 19020: https://bugs.ruby-lang.org/issues/19020

Add a test case to make sure the common thread doesn't leak to another ThreadGroup

https://github.com/ruby/timeout/commit/c4f1385c9a

[ruby/timeout] Give a name to the background thread

2022-07-13T12:16:15+00:00

https://github.com/ruby/timeout/commit/5594ae2f4d

[ruby/timeout] Keep a private reference to `Process.clock_gettime`

2022-06-09T09:58:49+00:00

`timeout 0.3.0` broke our test suite because we have some
tests that stubs `Process.clock_gettime` making it return
a value in the past, causing `Timeout` to trigger almost immediately.

I beleive it wasn't a problem before because it was relying on `Process.sleep`.

https://github.com/ruby/timeout/commit/e5911a303e

[ruby/timeout] Set the flag surely before return

2022-05-25T10:50:47+00:00

https://github.com/ruby/timeout/commit/f3a31abdfb

[ruby/timeout] Hack to avoid leak checker

2022-05-25T09:47:26+00:00

https://github.com/ruby/timeout/commit/9a9b03b44c

[ruby/timeout] Bump version to 0.3.0

2022-05-25T09:08:01+00:00

https://github.com/ruby/timeout/commit/f69f954a94

[ruby/timeout] Remove redundant done? check

2022-05-18T22:19:42+00:00

* It's already checked inside #interrupt.

https://github.com/ruby/timeout/commit/5f43254f81

[ruby/timeout] Synchronize all accesses to @done

2022-05-18T22:19:41+00:00

* So it is trivially correct.
* Performance seems the same overall.

https://github.com/ruby/timeout/commit/5e0d8e1637

[ruby/timeout] Handle Timeout + fork and add test for it

2022-05-18T22:19:40+00:00

https://github.com/ruby/timeout/commit/4baee63b9b