-
Notifications
You must be signed in to change notification settings - Fork 33
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
LeapSecondTable inverse bug? #42
Comments
Here is a better explanation.
As we increment TAI you can see the that the UTC leap second transition occurs at 2015-06-30 23:58:48.0 UTC, but I'm pretty sure it's supposed to occur at 2015-06-30 23:59:60.0 UTC. |
Iterating UTC and watching TAI, however, looks good, the UTC transition occurs at 2015-07-01 00:00:00.0 UTC.
|
Oh, of course the reason why this behavior is weird is that Data.Thyme.UTCTime doesn't support leap seconds. |
Actually the whole thing is buggy. :-/ There will be a fix soon. |
After applying @kim 's patch for #38 to load a
LeapSecondTable
, I see this.Lookup UTC -> TAI
Lookup (UTC -> TAI) -> UTC
I think both expressions should return
35s
? Is this a bug?The text was updated successfully, but these errors were encountered: