issue_comments: 734951187
This data as json
| html_url | issue_url | id | node_id | user | created_at | updated_at | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| https://github.com/pydata/xarray/issues/4045#issuecomment-734951187 | https://api.github.com/repos/pydata/xarray/issues/4045 | 734951187 | MDEyOklzc3VlQ29tbWVudDczNDk1MTE4Nw== | 2418513 | 2020-11-27T18:47:26Z | 2020-11-27T18:51:00Z | NONE | Just stumbled upon this as well. Internally, Simply telling it to Is there a way out of this, other than not using This is a huge issue, as anyone using nanosecond-precision timestamps with xarray would unknowingly and silently read wrong data after deserializing. |
{
"total_count": 2,
"+1": 2,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
614275938 |