Ruby Issue Tracking System

08/04/2019

02:54 AM Ruby Revision 982208c6 (git): [ruby/rexml] use #inspect to print meta-characters in error messages

https://github.com/ruby/rexml/commit/a124a19b9a gfx (Goro FUJI)

11/28/2018

01:29 AM Ruby Feature #15352 (Open): Mandatory block parameters

There are too many block parameter assertions (it's kind of idioms: [`raise NoBlockGiven unless glock_given?`](https://github.com/search?q=raise+NoBlockGiven+unless+block_given&type=Code)).
It's very useful if there's a syntax to decl... gfx (Goro FUJI)

03/29/2018

01:39 AM Ruby Bug #14432: Ruby crashes with "[BUG] pthread_mutex_destroy: Device or resource busy (EBUSY)"

This issue is no longer reproduced after upgrading Ruby to v2.5.0, as normalperson predicted. Thanks. gfx (Goro FUJI)

03/16/2018

06:12 AM Ruby Feature #11541: Let attr_accessor, _reader & _writer return symbols of the defined methods

+1
I'm about to issue the same feature request😆 gfx (Goro FUJI)

02/28/2018

08:20 AM Ruby Bug #14558: "Backtrace in reverse order" always upsets my brain!

mrkn (Kenta Murata) wrote:
> > it sometimes "reversed", sometimes "non-reversed"
> ...
Might be acceptable, or at least it's better than the current "random" order.
Why not provide a way to customize it, for example `RubyVM.backtr... gfx (Goro FUJI)

07:37 AM Ruby Bug #14558 (Closed): "Backtrace in reverse order" always upsets my brain!

A Ruby 2.5.0 feature "backtrace in reverse order", issued in https://bugs.ruby-lang.org/issues/8661, is confusing in developing Rails applications because I can't expect the order: it sometimes "reversed", sometimes "non-reversed". It ju... gfx (Goro FUJI)

02/02/2018

06:51 AM Ruby Bug #14432 (Closed): Ruby crashes with "[BUG] pthread_mutex_destroy: Device or resource busy (EBUSY)"

We notice that sidekiq (sidekiq pro) workers crash by `rb_bug_errno()`.
The very line that the issue raised is here: https://github.com/ruby/ruby/blob/v2_4_2/thread_pthread.c#L260
```c
static void
native_mutex_destroy(pthread_mut... gfx (Goro FUJI)

09/26/2013

04:05 PM Ruby Feature #8953 (Closed): `str =~ /pattern/` does not call =~ method if (1) str is a String, (2) /pattern/ is a Regexp literal

The expression `a =~ b` does not call the =~ method in some cases.
I think it is a bug that results from optimizations.
See the following code for details:
Code that does not work as expected (shows nothing):
$ ruby -e 's = "fo... gfx (Goro FUJI)