issue_comments: 523659811
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/3237#issuecomment-523659811 | https://api.github.com/repos/pydata/xarray/issues/3237 | 523659811 | MDEyOklzc3VlQ29tbWVudDUyMzY1OTgxMQ== | 1217238 | 2019-08-21T21:38:26Z | 2019-08-21T21:38:26Z | MEMBER | Yes, this is definitely a bug -- thanks for clear example to reproduce it! These helper functions were originally added back in https://github.com/pydata/xarray/pull/1883 to handle object dtype arrays properly. So it would be nice to fix this for object arrays in dask, but for the much more common non-object dtype arrays we should really just be using |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
483280810 |