issue_comments: 462134943
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/pull/2668#issuecomment-462134943 | https://api.github.com/repos/pydata/xarray/issues/2668 | 462134943 | MDEyOklzc3VlQ29tbWVudDQ2MjEzNDk0Mw== | 6628425 | 2019-02-10T13:55:55Z | 2019-02-10T13:55:55Z | MEMBER |
No worries @fujiisoup, this is totally fine with me. I think the most common use case for datetime arrays is in indexes, which currently need to be stored in memory anyway, so I don't think the dask use case would come up very often. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
398468139 |