-
Bug
-
Resolution: Fixed
-
Normal
-
None
-
None
This happened after migration to postgres. The default precision is float and we were using extract(epoch from ts) to obtain timestamps which had float precision. But, now we plan on passing datetime objects in listenstore instead of epochs.
Once that is complete, this problem can be solved easily.
Since the precision that user submits will also have seconds, hence it won't affect the functionality.
listenstore uses timestamps as float
-
Bug
-
Resolution: Fixed
-
Normal
-
None
-
None
This happened after migration to postgres. The default precision is float and we were using extract(epoch from ts) to obtain timestamps which had float precision. But, now we plan on passing datetime objects in listenstore instead of epochs.
Once that is complete, this problem can be solved easily.
Since the precision that user submits will also have seconds, hence it won't affect the functionality.