-
Notifications
You must be signed in to change notification settings - Fork 129
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
UI assumes epochs are in milliseconds #244
Comments
31K years in future will make you still 12 symbols in seconds so i would argue it's quite safe to assume if timestamp is 11 symbols or longer, that's milliseconds. also could check if it's 1970, probably wrong format picked. couple simple if cases and issue would be resolved :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
I have noticed that it seems when an epoch is rendered in the table view, it seems to assume that the epoch is in milliseconds (a javascript thing) rather than seconds.
I'm storing an expiry time as a TTL value for dynamoDB, which is always a value in seconds. When I hover over the value, the popup will always show a date in 1970.
I guess there's no real way of knowing which time format is being used in the table, and either way some users are going to miss out? Question is do more people use milliseconds or seconds for the epoch?
Just thought it was worth mentioning
The text was updated successfully, but these errors were encountered: