Skip to content

BUG: Datetime serialized to SECONDS from Unix epoch rather than MILLISECONDS from Unix epoch #61

@hcpchris

Description

@hcpchris

When a Python datetime.datetime instance (or Pandas Ttimestamp() is being serialized to a JS literal, it currently gets serialized as seconds from the Unix epoch. This leads to incorrect visualization, since it should be serialized as milliseconds from the Unix epoch. This bug needs to be fixed promptly.

See #60 for an example of this behavior.

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions