issue_comments: 806096033
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/5056#issuecomment-806096033 | https://api.github.com/repos/pydata/xarray/issues/5056 | 806096033 | MDEyOklzc3VlQ29tbWVudDgwNjA5NjAzMw== | 1217238 | 2021-03-24T19:29:13Z | 2021-03-24T19:29:13Z | MEMBER | These both sound fine to me. So far, I've been happy working around (1) by constructing synthetic dask arrays with the desired final chunks. I suspect that's even pretty efficient on the dask side, as long as everything uses Dask's |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
836391524 |