This project is archived and is in readonly mode.
ActiveSupport::TimeWithZone#period raises an exception when using a nil timezone
Reported by Aaron Patterson | June 17th, 2010 @ 12:44 AM | in 3.x
Sometimes ::Time.zone can return a nil. When a ActiveSupport::TimeWithZone is created with a nil timezone, the period method raises an exception.
I've attached a patch with a test and potential fix.
Comments and changes to this ticket
-
Aaron Patterson June 17th, 2010 @ 12:46 AM
- Tag set to “patch”
-
-
-
Aaron Patterson June 17th, 2010 @ 10:12 PM
Yay! Another patch, after talk to Jeremy about the problem.
-
Repository June 17th, 2010 @ 10:17 PM
- State changed from “new” to “resolved”
(from [5ae7a9d31d6222b265013ab450f9d30b88113e69]) when the timezone is nil, a TimeWithZone object should not be constructed. [#4881 state:resolved]
Signed-off-by: Jeremy Kemper jeremy@bitsweat.net
http://github.com/rails/rails/commit/5ae7a9d31d6222b265013ab450f9d3...
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
<h2 style="font-size: 14px">Tickets have moved to Github</h2>
The new ticket tracker is available at <a href="https://github.com/rails/rails/issues">https://github.com/rails/rails/issues</a>
People watching this ticket
Aaron Patterson
Jeremy Kemper
Santiago Pastorino
Attachments
Tags
Referenced by
-
4881
ActiveSupport::TimeWithZone#period raises an exception when using a nil timezone
(from [5ae7a9d31d6222b265013ab450f9d30b88113e69])
when th...