LeapSecondTable inverse bug?

Open
#42 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
haskell
Domain
backend

Research direction

Start by reproducing the two leapSecondTable expressions shown in the issue, using the LeapSecondTable path introduced by #38. Trace the UTC-to-TAI result through its inverse conversion and verify whether both lookups should produce 35s; done means the discrepancy is explained and covered by a regression test.

Written by the indexing model from the issue text.

Description

After applying @kim 's patch for #38 to load a LeapSecondTable, I see this.

Lookup UTC -> TAI

> leapSecondTable $ Left $ mkUTCTime (fromGregorian 2015 6 30) (hhmmss 23 59 59)
35s

Lookup (UTC -> TAI) -> UTC

> leapSecondTable $ Right $ mkUTCTime (fromGregorian 2015 6 30) (hhmmss 23 59 59) ^. absoluteTime leapSecondTable 
36s

I think both expressions should return 35s? Is this a bug?

Dominant language
Haskell
Stars
47
Forks
35
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from haskell-github-trust/thyme

All issues in haskell-github-trust/thyme

Similar issues

More Haskell issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.