From: "hsbt (Hiroshi SHIBATA) via ruby-core" <ruby-core@...>
Date: 2023-02-07T06:04:40+00:00
Subject: [ruby-core:112251] [Ruby master Bug#19407] 2 threads taking from current ractor will hang forever

Issue #19407 has been updated by hsbt (Hiroshi SHIBATA).

Status changed from Open to Assigned
Assignee set to ko1 (Koichi Sasada)

----------------------------------------
Bug #19407: 2 threads taking from current ractor will hang forever
https://bugs.ruby-lang.org/issues/19407#change-101679

* Author: luke-gru (Luke Gruber)
* Status: Assigned
* Priority: Normal
* Assignee: ko1 (Koichi Sasada)
* Backport: 2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN
----------------------------------------
In the current implementation of Ractors, it's possible to `take` from the current ractor. This could be useful
when co-ordinating threads:

```ruby
t = Thread.new do
  obj = Ractor.current.take
  p obj # do some work with obj
end
t0 = Thread.new do
  obj = Ractor.current.take
  p obj # do some work with obj
end
Ractor.yield :go
```

However it hangs forever:

```ruby
t = Thread.new do
  obj = Ractor.current.take
  p obj
end
t0 = Thread.new do
  obj = Ractor.current.take
  p obj
end
sleep 0.5
```

Should "self-take" be disabled, or was it designed to allow it but this is just a bug?



-- 
https://bugs.ruby-lang.org/
 ______________________________________________
 ruby-core mailing list -- ruby-core@ml.ruby-lang.org
 To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org
 ruby-core info -- https://ml.ruby-lang.org/mailman3/postorius/lists/ruby-core.ml.ruby-lang.org/