[#90399] [Ruby trunk Feature#14813] [PATCH] gc.c: make gc_enter+gc_exit pairs dtrace probes, too — ko1@...
Issue #14813 has been updated by ko1 (Koichi Sasada).
3 messages
2018/12/10
[#90417] [Ruby trunk Bug#15398] TestThread#test_signal_at_join fails on FreeBSD — naruse@...
Issue #15398 has been reported by naruse (Yui NARUSE).
4 messages
2018/12/11
[#90423] Re: [Ruby trunk Bug#15398] TestThread#test_signal_at_join fails on FreeBSD
— Eric Wong <normalperson@...>
2018/12/11
naruse@airemix.jp wrote:
[#90519] Spoofing warnings for mail from bugs.ruby-lang.org — Charles Oliver Nutter <headius@...>
I'm getting a spoofing warning for emails sent from bugs.ruby-lang.org when
4 messages
2018/12/13
[#90522] Re: Spoofing warnings for mail from bugs.ruby-lang.org
— Eric Wong <normalperson@...>
2018/12/13
Charles Oliver Nutter <headius@headius.com> wrote:
[#90533] [Ruby trunk Feature#15413] unmarkable C stack (3rd stack) — normalperson@...
Issue #15413 has been reported by normalperson (Eric Wong).
3 messages
2018/12/14
[#90581] [Ruby trunk Bug#15424] Ruby 2.6.0rc1 & 2.6.0rc2 mutex exception — mat999@...
Issue #15424 has been reported by splitice (Mathew Heard).
3 messages
2018/12/17
[#90595] [Ruby trunk Bug#15430] test_fork_while_parent_locked is failing status on Ruby CI — hsbt@...
Issue #15430 has been reported by hsbt (Hiroshi SHIBATA).
3 messages
2018/12/18
[#90614] [Ruby trunk Bug#15430][Assigned] test_fork_while_parent_locked is failing status on Ruby CI — hsbt@...
Issue #15430 has been updated by hsbt (Hiroshi SHIBATA).
4 messages
2018/12/19
[#90630] Re: [Ruby trunk Bug#15430][Assigned] test_fork_while_parent_locked is failing status on Ruby CI
— Eric Wong <normalperson@...>
2018/12/20
> It still exists. https://rubyci.org/logs/rubyci.s3.amazonaws.com/centos7/ruby-trunk/log/20181218T230003Z.fail.html.gz
[#90820] Re: [ruby-cvs:73697] k0kubun:r66593 (trunk): accept_nonblock_spec.rb: skip spurious failure — Eric Wong <normalperson@...>
k0kubun@ruby-lang.org wrote:
3 messages
2018/12/30
[ruby-core:90693] [CommonRuby Feature#15458] Automatic Exception#cause print in IRB
From:
me@...
Date:
2018-12-24 07:07:54 UTC
List:
ruby-core #90693
Issue #15458 has been reported by jnchito (Junichi Ito).
----------------------------------------
Feature #15458: Automatic Exception#cause print in IRB
https://bugs.ruby-lang.org/issues/15458
* Author: jnchito (Junichi Ito)
* Status: Open
* Priority: Normal
* Assignee:
* Target version:
----------------------------------------
According to Ruby 2.6 NEWS, the following feature will be added:
> Print cause of the exception if the exception is not caught and printed its backtraces and error message [Feature #8257]
I expected it would be applied in IRB too, but it wasn't. Here is my example:
~~~
> begin
> 1/0
> rescue => e
> e.mesage
> end
Traceback (most recent call last):
5: from /Users/jnito/.rbenv/versions/2.6.0-rc1/bin/irb:23:in `<main>'
4: from /Users/jnito/.rbenv/versions/2.6.0-rc1/bin/irb:23:in `load'
3: from /Users/jnito/.rbenv/versions/2.6.0-rc1/lib/ruby/gems/2.6.0/gems/irb-0.9.6/exe/irb:11:in `<top (required)>'
2: from (irb):1
1: from (irb):4:in `rescue in irb_binding'
NoMethodError (undefined method `mesage' for #<ZeroDivisionError: divided by 0>)
Did you mean? message
~~~
On the other hand, when I run that code via ruby command, cause of the exception is automatically printed:
~~~
$ ruby sample.rb
Traceback (most recent call last):
1: from sample.rb:2:in `<main>'
sample.rb:2:in `/': divided by 0 (ZeroDivisionError)
1: from sample.rb:1:in `<main>'
sample.rb:4:in `rescue in <main>': undefined method `mesage' for #<ZeroDivisionError: divided by 0> (NoMethodError)
Did you mean? message
~~~
I feel it would be more natural and useful if the new feature would work in IRB too.
--
https://bugs.ruby-lang.org/
Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>