Project

General

Profile

Bug #6887

Time.zone.now returning different timezone that Time.zone.at

Added by anthfb (Anthony Figueroa) about 8 years ago. Updated about 8 years ago.

Status:
Third Party's Issue
Priority:
Normal
Assignee:
-
Target version:
ruby -v:
ruby 1.9.2p290 (2011-07-09 revision 32553) [x86_64-darwin10.8.0]
Backport:
[ruby-core:47233]

Description

1.9.2p290 :018 > Time.zone = 'Brasilia'
=> "Brasilia"

1.9.2p290 :020 > Time.zone.now
=> Fri, 17 Aug 2012 13:08:06 BRT -03:00

1.9.2p290 :021 > Event.last.start_time
=> 2000-01-01 03:45:00 UTC

1.9.2p290 :022 > Time.zone.at(event.start_time)
=> Sat, 01 Jan 2000 01:45:00 BRST -02:00

Why is this happening? Is it a bug?

Updated by drbrain (Eric Hodel) about 8 years ago

  • Status changed from Open to Rejected

Brazil uses daylight savings time. Jan 1 is in standard time, Aug 17th is in daylight savings time:

http://www.timeanddate.com/worldclock/timezone.html?n=45

#2

Updated by drbrain (Eric Hodel) about 8 years ago

Oops, I got the direction backwards, but the behavior is still expected.

Updated by nobu (Nobuyoshi Nakada) about 8 years ago

  • Status changed from Rejected to Third Party's Issue

=begin
No such methods, (({Time#zone})) and (({Time#zone=})), are defined.
Probably ActiveSupport or similar gems.
=end

Also available in: Atom PDF