issue_comments: 554648042
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/3535#issuecomment-554648042 | https://api.github.com/repos/pydata/xarray/issues/3535 | 554648042 | MDEyOklzc3VlQ29tbWVudDU1NDY0ODA0Mg== | 6628425 | 2019-11-16T15:39:23Z | 2019-11-16T15:39:23Z | MEMBER | Thanks for raising this issue @mathause. In hindsight this does not surprise me. Pandas's strict use of nanosecond-resolution datetimes and timedeltas was part of the motivation for the Perhaps a more robust (yet more complex) solution for https://github.com/pydata/xarray/issues/2484 would be to write a version of a Regarding the It appears if we just select the first value of each index (i.e. a
```
|
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
523037716 |