[#60404] is RB_GC_GUARD needed in rb_io_syswrite? — Eric Wong <normalperson@...>
I haven't gotten it to crash as-is, but it seems like we need to
4 messages
2014/02/01
[#60682] volatile usages — Eric Wong <normalperson@...>
Hi all, I went ahead and removed some use of volatile which were once
5 messages
2014/02/13
[#60794] [RFC] rearrange+pack vtm and time_object structs — Eric Wong <normalperson@...>
Extracted from addendum on top of Feature #9362 (cache-aligned objects).
4 messages
2014/02/16
[#61139] [ruby-trunk - Feature #9577] [Open] [PATCH] benchmark/driver.rb: align columns in text output — normalperson@...
Issue #9577 has been reported by Eric Wong.
3 messages
2014/02/28
[ruby-core:60464] [ruby-trunk - Bug #9032] Time.round reverts the DST status of the time
From:
usa@...
Date:
2014-02-05 02:46:19 UTC
List:
ruby-core #60464
Issue #9032 has been updated by Usaku NAKAMURA. Backport deleted (1.9.3: UNKNOWN, 2.0.0: UNKNOWN) ---------------------------------------- Bug #9032: Time.round reverts the DST status of the time https://bugs.ruby-lang.org/issues/9032#change-44929 * Author: Mayank Sharma * Status: Third Party's Issue * Priority: Normal * Assignee: * Category: * Target version: * ruby -v: ruby 2.0.0p0 (2013-02-24 revision 39474) [x86_64-darwin11.4.2] * Backport: ---------------------------------------- =begin If the time is in non-DST and round method is applied, then the resulting time goes back to DST time. This happens only during the 1 hour when time goes back. Following example should explain the situation better. 2.0.0-p0 :057 > d => Sun, 27 Oct 2013 02:30:00 CET +01:00 2.0.0-p0 :058 > d.isdst => false 2.0.0-p0 :059 > d.round(3) => Sun, 27 Oct 2013 02:30:00 CEST +02:00 2.0.0-p0 :060 > d.round(3).isdst => true I have set the priority Urgent as the DST is going to elapse in 10 days from now. =end -- http://bugs.ruby-lang.org/