nvashchenko (Nikolay Vashchenko)
- Login: nvashchenko
- Registered on: 02/21/2017
- Last sign in: 06/05/2017
Issues
| open | closed | Total | |
|---|---|---|---|
| Assigned issues | 0 | 0 | 0 |
| Reported issues | 0 | 2 | 2 |
Activity
07/17/2017
-
04:22 AM Ruby Bug #13632: Not processable interrupt queue for a thread after it's notified that FD is closed in some other thread.
- I created a gem with a temporary workaround for versions 2.2.7, 2.3.4 and 2.4.1 to help folks until versions with backports are released:
https://rubygems.org/gems/stopgap_13632
06/05/2017
-
04:16 PM Ruby Bug #13632 (Closed): Not processable interrupt queue for a thread after it's notified that FD is closed in some other thread.
- In the bugfix for https://bugs.ruby-lang.org/issues/13076 has been introduced another bug, caused by a busy waiting in rb_notify_fd_close method, while the FD is being released. During this waiting, it pumps huge amounts of the ruby_erro...
02/25/2017
-
03:25 AM Ruby Bug #13239: Bug with "special exceptions" when they are thrown in context of a rescue clause.
- Yes, that appears to be the case, thanks you.
02/21/2017
-
06:22 AM Ruby Bug #13239: Bug with "special exceptions" when they are thrown in context of a rescue clause.
- Oops, wrong link to the ruby fork.
Here's the right one: https://github.com/NickolasVashchenko/ruby/commits/special_exc_cause_bug -
06:19 AM Ruby Bug #13239 (Closed): Bug with "special exceptions" when they are thrown in context of a rescue clause.
- I've stumbled upon a case when ruby is supposed to throw "IOError: stream closed"(https://github.com/ruby/ruby/blob/trunk/thread.c#L4823) because there was a retained FD lock by another thread, but I'm was getting this instead of it:
...