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
The timestamp parameter in the params object doesn't behave as I would expect according to the documentation https://www.mindmeld.com/docs/userguide/dm.html?highlight=timestamp#params
It is listed as a unix timestamp which should be represented in seconds, however the handling of it attempts to differentiate between a seconds and milliseconds measurement. https://github.com/cisco/mindmeld/blob/master/mindmeld/ser.py#L151
The API definition should include the units and the behaviour should follow the definition.
The current method of checking the number of digits in the timestamp is not robust. This causes confusing behaviour when using timestamps older than 2001.
The text was updated successfully, but these errors were encountered:
davidmfrey
changed the title
timestamp parameter has strange behaviour
timestamp parameter has inconsistent behaviour
Jun 14, 2019
The timestamp parameter in the params object doesn't behave as I would expect according to the documentation
https://www.mindmeld.com/docs/userguide/dm.html?highlight=timestamp#params
It is listed as a unix timestamp which should be represented in seconds, however the handling of it attempts to differentiate between a seconds and milliseconds measurement.
https://github.com/cisco/mindmeld/blob/master/mindmeld/ser.py#L151
The API definition should include the units and the behaviour should follow the definition.
The current method of checking the number of digits in the timestamp is not robust. This causes confusing behaviour when using timestamps older than 2001.
The text was updated successfully, but these errors were encountered: