[#29911] [Bug #3231] Digest Does Not Build — Charlie Savage <redmine@...>

Bug #3231: Digest Does Not Build

19 messages 2010/05/01

[#29920] [Feature #3232] Loops (while/until) should return last statement value if any, like if/unless — Benoit Daloze <redmine@...>

Feature #3232: Loops (while/until) should return last statement value if any, like if/unless

9 messages 2010/05/01

[#29997] years in Time.utc — Xavier Noria <fxn@...>

Does anyone have a precise statement about the years supported by

13 messages 2010/05/04

[#30010] [Bug #3248] extension 'tk' is finding tclConfig.sh and tkConfig.sh incorrectly — Luis Lavena <redmine@...>

Bug #3248: extension 'tk' is finding tclConfig.sh and tkConfig.sh incorrectly

9 messages 2010/05/05

[#30226] [Bug #3288] Segmentation fault - activesupport-3.0.0.beta3/lib/active_support/callbacks.rb:88 — Szymon Jeż <redmine@...>

Bug #3288: Segmentation fault - activesupport-3.0.0.beta3/lib/active_support/callbacks.rb:88

10 messages 2010/05/13

[#30358] tk doesn't startup well in doze — Roger Pack <rogerdpack2@...>

Currently with 1.9.x and tk 8.5,the following occurs

12 messages 2010/05/22

[ruby-core:30074] Re: [Bug #3212] ConditionVariable may become inconsistent for interrupted threads

From: Yusuke ENDOH <mame@...>
Date: 2010-05-07 00:47:44 UTC
List: ruby-core #30074
Hi,

2010/5/7 Caleb Clausen <vikkous@gmail.com>:
>> This is a serious issue, but if this is fixed to ensure to lock
>> the mutex by ignoring an exception, the process can not be
>> stopped by Ctrl+C. ?It is another serious issue.
>
> I can't say I entirely understand. Do you mean that ignoring the 2nd
> Thread#raise causes ctrl-c to be ignored?

Exactly.


> Can a special case for
> ctrl-c be made? Is there a more complete discussion of this issue
> somewhere?

Sorry, this is discussed in Japanese closed IRC with some committers
including ko1, akr and kosaki.  To sum up the discussion, we thought
convenience of Ctrl+C is more important (for casual users) then
consistency of CV#wait.
And, a techie who want consistency of CV#wait can achieve it by
avoiding Thread#raise and by paying attention to signal.


>> In addition, if we are really serious for using CV, signal must
>> not be converted to an exception, such as SIGINT and Interrupted.
>> It can be achieved by Kernel#trap, i.e., trap(:INT) {}, but it
>> is too stoic to enjoy programming...
>
> All signals are sent to the main thread, aren't they? So at least the
> user needs to worry about this only if using a CV in the main thread.

Exactly.  You are really quine to understand :-)

-- 
Yusuke Endoh <mame@tsg.ne.jp>

In This Thread