-
-
Notifications
You must be signed in to change notification settings - Fork 663
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
Updated to latest, string unix timestamp is not understood by 'get' #1117
Labels
Comments
sebtrack
changed the title
Updated to latest string unix timestamp is not understood by 'get'
Updated to latest, string unix timestamp is not understood by 'get'
Jul 14, 2022
@krisfremen @systemcatch @jadchaar any insight on this? |
From reading the release history, this behavior was intentionally changed in version 0.15.0 "to support the ISO 8601 basic format and to address bugs such as #447". Is this really something that people would want to revert? |
@krisfremen @jadchaar @systemcatch could you elaborate more for @13MK3 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue Description
results in
worked beforehand but with the latest version it does not.
We would like to accept a lot of time formats and some of them are strings some of them are unix timestamps, so forcing a int/float conversion is unacceptable. It would be nice to use string unix timestamps.
System Info
The text was updated successfully, but these errors were encountered: