issue_comments: 747777810
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/4704#issuecomment-747777810 | https://api.github.com/repos/pydata/xarray/issues/4704 | 747777810 | MDEyOklzc3VlQ29tbWVudDc0Nzc3NzgxMA== | 1217238 | 2020-12-17T23:51:57Z | 2020-12-17T23:51:57Z | MEMBER | This does happen with some other backends, specifically netCDF and pydap when access remote datasets via HTTP/opendap. We have a I think exponential backoff with fuzzing is the right strategy for rare network failures, but I would suggest trying to push this to as low of a level as possible, e.g., ideally inside gcsfs. Retrying the whole dask computation seems quite wasteful. |
{ "total_count": 2, "+1": 2, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
770006670 |