From: ko1@atdot.net
To: ruby-dev@ruby-lang.org
Subject: [ruby-dev:50985] [Ruby master Bug#17482] Ractor.receive doesnt accept Ctrl+C under some condition
Date: Sun, 27 Dec 2020 14:28:19 +0000 (UTC) [thread overview]
Message-ID: <redmine.journal-89566.20201227142818.4973@ruby-lang.org> (raw)
In-Reply-To: <redmine.issue-17482.20201227134126.4973@ruby-lang.org>
Issue #17482 has been updated by ko1 (Koichi Sasada).
Assignee set to ko1 (Koichi Sasada)
Status changed from Open to Assigned
Thank you for the report, I could reproduce it.
----------------------------------------
Bug #17482: Ractor.receive doesnt accept Ctrl+C under some condition
https://bugs.ruby-lang.org/issues/17482#change-89566
* Author: riskwa (riskwa anon)
* Status: Assigned
* Priority: Normal
* Assignee: ko1 (Koichi Sasada)
* ruby -v: ruby 3.0.0p0 (2020-12-25 revision 95aff21468) [x86_64-linux]
* Backport: 2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: UNKNOWN
----------------------------------------
When I run this script, Ctrl+C doesn't work.
Waiting forever on #4 is fine, but I think Ctrl+C should work.
``` ruby
r = Ractor.new() {
# sleep 1 #1
File.open(__FILE__){ } #2
}
# sleep 1 #3
p Ractor.receive #4
```
When I comment out #2, Ctrl+C works.
When I comment in #1 and/or #3, Ctrl+C works.
In my environment, it's reproducable in 100%.
My environment is:
WSL2 ubuntu 5 4.19.128-microsoft-standard #1 i5-10400 6core
--
https://bugs.ruby-lang.org/
next prev parent reply other threads:[~2020-12-27 14:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-27 13:41 [ruby-dev:50984] " rrr_one_1
2020-12-27 14:28 ` ko1 [this message]
2021-02-05 6:34 ` [ruby-dev:51015] " ko1
2021-02-08 10:54 ` [ruby-dev:51017] " naruse
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=redmine.journal-89566.20201227142818.4973@ruby-lang.org \
--to=ko1@atdot.net \
--cc=ruby-dev@ruby-lang.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).