You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Those values should all be integers. Some kind of improper computation is going on here.
These discrepancies are significant, because if I pass in a Unix time of e.g. -265680000000 for conversion, it ends up falling on the wrong side of a boundary where the TAI/Unix offset changed, and returning an incorrect result.
Worst-case scenario, it may be necessary to pre-compute these values. Hmm.
The text was updated successfully, but these errors were encountered:
As per issue #2. Will probably have to do the same for Unix block start
times as per #3. And end times, in fact, since the Unix block end time
*isn't* the same as the start time of the previous block... it's not
even a precise number of Unix seconds offset, it's a precise number of
*TAI* seconds offset!!
Those values should all be integers. Some kind of improper computation is going on here.
These discrepancies are significant, because if I pass in a Unix time of e.g. -265680000000 for conversion, it ends up falling on the wrong side of a boundary where the TAI/Unix offset changed, and returning an incorrect result.
Worst-case scenario, it may be necessary to pre-compute these values. Hmm.
The text was updated successfully, but these errors were encountered: