-
Notifications
You must be signed in to change notification settings - Fork 361
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
truncate overflows when handling times in milliseconds #1079
Comments
matsjoyce
changed the title
truncate overflows when handling time
truncate overflows when handling times in milliseconds
Feb 19, 2020
Thanks for reporting this! To set expectations:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: