[#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:90542] [Ruby trunk Feature#15195] How to deal with new Japanese era
From:
duerst@...
Date:
2018-12-15 03:03:17 UTC
List:
ruby-core #90542
Issue #15195 has been updated by duerst (Martin Dテシrst). According to https://www.japantimes.co.jp/news/2018/12/06/national/politics-diplomacy/japan-mulls-announcing-new-era-name-april-11-sources/#.XBQPC6qWxD8, the announcement of the new area name may be postponed until about April 11. ---------------------------------------- Feature #15195: How to deal with new Japanese era https://bugs.ruby-lang.org/issues/15195#change-75692 * Author: duerst (Martin Dテシrst) * Status: Open * Priority: Normal * Assignee: * Target version: ---------------------------------------- As most people in Japan should know by now, a new era of the Japanese calendar will start in May 2019. It is not clear when the new era name will be announced, but it may be at rather short notice. The Unicode consortium has made up a plan about how to deal with this, see http://blog.unicode.org/2018/09/new-japanese-era.html. Among else, they will encode an equivalent of the current 纃ス, 纃シ, 纃サ, and plan to publish a special version of the Unicode standard numbered 12.1. We should start to discuss and tentatively decide what (if anything) will be needed for Ruby. Alternatives include the following two and others inbetween. * Follow past years where the update to a new Unicode version is done with the Ruby version release around Christmas. That would mean we upgrade to Unicode 12 around Christmas 2019. At that time, we can include the changes in 12.1 without any problems. * Implement the upgrade to Unicode 12 as quickly as possible in trunk, implement Unicode 12.1 as soon as available in trunk, and backport the changes needed for the new era name to older Ruby versions. -- 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>