IPstack/AIP epoch. Year 2038 problem
Nobody has claimed this yet.
- Dominant language
- Ada
- Stars
- 328
- Forks
- 47
- PR merge metrics
- No merged PRs in 30d
Description
The support files aip-time_types.ads mention an unspecified epoch.
This will likely be Jan 1st 1970, however that is susceptible to overflow in 2038. A user could use a more recent epoch to buy e.g. 50 years.
The best way to fix it would be for the type Time to be mod 2 ** 64.
Would a PR be welcome? It would likely require users to update their support files.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the support file aip-time_types.ads and inspect how the Time type and epoch are defined. Assess the proposed epoch and 64-bit representation, including the compatibility impact for users who would need to update their support files; done means a maintainer-approved design and corresponding support-file changes.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100