issue_comments: 1264523142
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/6803#issuecomment-1264523142 | https://api.github.com/repos/pydata/xarray/issues/6803 | 1264523142 | IC_kwDOAMm_X85LXxeG | 33886395 | 2022-10-02T01:29:35Z | 2022-10-02T01:29:35Z | NONE | I think I may have narrowed down the problem to a limitation in dask using dask_gateway. If passing a Future to a worker, the worker will try to unpickle that Future, and as part of that unpickle the Client object passed when creating such Future. Unfortunately, in a dask_gateway context the client is behind a |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
1307523148 |