issue_comments: 417380229
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/2389#issuecomment-417380229 | https://api.github.com/repos/pydata/xarray/issues/2389 | 417380229 | MDEyOklzc3VlQ29tbWVudDQxNzM4MDIyOQ== | 1217238 | 2018-08-30T16:24:07Z | 2018-08-30T16:24:07Z | MEMBER | OK, so it seems like the complete solution here should involve refactoring our backend classes to avoid any references to objects storing dask graphs. This is a cleaner solution even regardless of the pickle overhead because it allows us to eliminate all state stored in backend classes. I'll get on that in #2261. |
{
"total_count": 1,
"+1": 1,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
355264812 |