From: Eric Wong <normalperson@yhbt.net>
To: ruby-core@ruby-lang.org
Subject: [ruby-core:81584] Re: [Ruby trunk Bug#13632] Not processable interrupt queue for a thread after it's notified that FD is closed in some other thread.
Date: Mon, 5 Jun 2017 21:51:27 +0000 [thread overview]
Message-ID: <20170605215127.GA29215@whir> (raw)
In-Reply-To: <redmine.issue-13632.20170605161653.c9f0d3627f5faa87@ruby-lang.org>
sir.nickolas@gmail.com wrote:
> Bug #13632: Not processable interrupt queue for a thread after it's notified that FD is closed in some other thread.
> https://bugs.ruby-lang.org/issues/13632
Investigating. I've been looking at IO close notification for
[Feature #13618] (auto-Fiber) anyways.
next prev parent reply other threads:[~2017-06-05 21:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-13632.20170605161653@ruby-lang.org>
2017-06-05 16:16 ` [ruby-core:81581] [Ruby trunk Bug#13632] Not processable interrupt queue for a thread after it's notified that FD is closed in some other thread sir.nickolas
2017-06-05 21:51 ` Eric Wong [this message]
2017-06-06 0:20 ` [ruby-core:81585] " Eric Wong
2017-06-07 20:05 ` [ruby-core:81613] " Eric Wong
2017-07-08 2:21 ` [ruby-core:81966] " nagachika00
2017-07-17 4:23 ` [ruby-core:82085] " sir.nickolas
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-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.ruby-lang.org/en/community/mailing-lists/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170605215127.GA29215@whir \
--to=ruby-core@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 read-only IMAP folder(s) and NNTP newsgroup(s).