-
Notifications
You must be signed in to change notification settings - Fork 458
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fails to parse "03/10/2013 12:00 AM" #228
Comments
I can't reproduce, it works fine for me. Most likly something with your timezone/environment. Could you provide more details (timezone, ruby, platform)? And try with newest Chronic 0.10.2 |
chronic (0.10.2) It's a timezone thing. We have our timezone set as follows:
When that is removed it works fine. |
Has there been any updates on this? I'm getting the following errors (all to do with DST starting) Chronic.parse("2014-03-09")
=> Sun, 09 Mar 2014 13:00:00 EDT -04:00 # Why is this at one in the afternoon?
Chronic.parse("2014-03-09 12:00 AM")
=> nil
Chronic.parse("2014-03-09 12:59 AM")
=> nil
Chronic.parse("2014-03-09 1:00 AM")
=> Sun, 09 Mar 2014 00:00:00 EST -05:00 # Why is this midnight?
Chronic.parse("2014-03-09 2 AM")
=> Sun, 09 Mar 2014 01:00:00 EST -05:00 # This has moved back by one hour
Chronic.parse("2014-03-09 12:00 PM")
=> Mon, 10 Mar 2014 00:00:00 EDT -04:00 # Why is this midnight of the next day? If I try any other times on that day after 2 AM that is not between noon and 1pm, the parsing is correct. |
There haven't been any updates regarding this issue, so it's not fixed. |
I'm getting the same thing: Chronic.parse "3/8/2014 11:59:59 PM"
=> 2014-03-08 23:59:59 -0500
Chronic.parse "3/9/2014 12:00:00 AM"
=> nil
Chronic.parse "3/9/2014 12:59:59 AM"
=> nil
Chronic.parse "3/9/2014 1:00:00 AM"
=> 2014-03-09 00:00:00 -0500
Time.zone.to_s
=> "(GMT-05:00) Eastern Time (US & Canada)" Ruby version: |
I'm also experiencing something similar:
Ruby version: |
Returns nil
The text was updated successfully, but these errors were encountered: