GNU Astronomy Utilities - Bugs: bug #61976, Table arithmetic date-to-sec...
You are not allowed to post comments on this tracker with your current authentication level.
bug #61976: Table arithmetic date-to-sec produces inaccurate result
Submitter: | Pedram Ashofteh-Ardakani <pedram> | ||
Submitted: | Tue 01 Feb 2022 06:18:37 PM UTC | ||
Category: | Table | Severity: | 3 - Normal |
Item Group: | Output not reasonable | Status: | Fixed |
Privacy: | Public | Assigned to: | makhlaghi |
Open/Closed: | Closed |
Fri 11 Feb 2022 02:36:39 PM UTC, comment #1: |
Mohammad Akhlaghi <makhlaghi> |
Tue 01 Feb 2022 06:18:37 PM UTC, original submission:
This bug was first reported by Zohreh Ghaffari.
steps to reproduce
|
Pedram Ashofteh-Ardakani <pedram> |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 5 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2022-02-11 | makhlaghi | Status | None | Fixed | |
Assigned to | None | makhlaghi | |||
Open/Closed | Open | Closed | |||
Carbon-Copy | - | Added -email is unavailable- | |||
2022-02-01 | pedram | Carbon-Copy | - | Added makhlaghi |
Powered by Savane 3.13-4b48.
Corresponding source code
Thanks for the great bug report Pedram! It has been fixed in Commit 8837a5a8a.
This was an important bug and it was always haunting me from the day I first implemented 'date-to-sec'! I knew that storing a many-significant-digit integer number (like number of seconds from 1970-01-01) into a 64-bit floating point type will be problematic, but I failed to act upon it then!
Hopefully the commit message has clarified the solution, so I won't repeat it anymore here ;-).