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
Same issue as #591 (tracked in #721). I am receiving a bunch of timestamps from an API as floating point seconds since the epoch. To process them I was doing:
Time.millisToPosix <| truncate <| t *1000
which causes an overflow, giving times before 1970. Changing to:
Time.millisToPosix <| round <| t *1000
fixed the issue, as would using ceiling. However, it would be nice if truncate could handle 64 bit floats without surprises.
The text was updated successfully, but these errors were encountered:
matsjoyce
changed the title
truncate overflows when handling time
truncate overflows when handling times in milliseconds
Feb 19, 2020
Issues are reviewed in batches, so it can take some time to get a response.
Ask questions a community forum. You will get an answer quicker that way!
If you experience something similar, open a new issue. We like duplicates.
Finally, please be patient with the core team. They are trying their best with limited resources.
Same issue as #591 (tracked in #721). I am receiving a bunch of timestamps from an API as floating point seconds since the epoch. To process them I was doing:
which causes an overflow, giving times before 1970. Changing to:
fixed the issue, as would using
ceiling
. However, it would be nice if truncate could handle 64 bit floats without surprises.The text was updated successfully, but these errors were encountered: