[#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
[email protected] 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 <[email protected]> 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@...>
[email protected] wrote:
3 messages
2018/12/30
[ruby-core:90468] [Ruby trunk Bug#13822] Time.dst?
From:
andrew_kim_2016@...
Date:
2018-12-13 01:18:30 UTC
List:
ruby-core #90468
Issue #13822 has been updated by kronikus (ANDREY KIM). Tracker changed from Feature to Bug Subject changed from Time.dst_changes(t=Time.now.year) to Time.dst? ruby -v set to ruby 2.4.3p205 (2017-12-14 revision 61247) [x86_64-linux] Backport set to 2.4: UNKNOWN, 2.5: UNKNOWN Is it bug or feature? Receiving same result for Time.dst? method. I belive it suppose to base it response on date in variable, correct me if i'm wrong. Receiving it in Rails 5.1.2, but Time class is in ruby core gems tzinfo, tzinfo-data are in Gemfile Time zone configured in rails config: 2.4.3 :001 > Time.zone => #<ActiveSupport::TimeZone:0x000055ac84e61410 @name="Eastern Time (US & Canada)", @utc_offset=nil, @tzinfo=#<TZInfo::DataTimezone: America/New_York>> 2.4.3 :013 > t => 2018-12-12 10:00:00 -0500 2.4.3 :014 > a => 2018-08-01 10:00:00 -0500 2.4.3 :015 > t.dst? => false 2.4.3 :016 > a.dst? => false 2.4.3 :017 > t.isdst => false 2.4.3 :018 > a.isdst => false ---------------------------------------- Bug #13822: Time.dst? https://bugs.ruby-lang.org/issues/13822#change-75626 * Author: opti (Andreas Opti) * Status: Feedback * Priority: Normal * Assignee: * Target version: * ruby -v: ruby 2.4.3p205 (2017-12-14 revision 61247) [x86_64-linux] * Backport: 2.4: UNKNOWN, 2.5: UNKNOWN ---------------------------------------- output [time1,time2] of daysaving-changes of given year I assume the result does not depend on timezone, only the output will be in default timezone. -- https://bugs.ruby-lang.org/ Unsubscribe: <mailto:[email protected]?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>