issues: 379177627
This data as json
| id | node_id | number | title | user | state | locked | assignee | milestone | comments | created_at | updated_at | closed_at | author_association | active_lock_reason | draft | pull_request | body | reactions | performed_via_github_app | state_reason | repo | type |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 379177627 | MDU6SXNzdWUzNzkxNzc2Mjc= | 2551 | HDF Errors since xarray 0.11 | 10050469 | closed | 0 | 10 | 2018-11-09T14:14:11Z | 2018-11-12T00:12:46Z | 2018-11-11T12:10:36Z | MEMBER | (EDIT: sorry for unexpected early posting) I just wanted to open this issue here, just to see if it has some resonance in other projects. We are getting new unexpected HDF Errors in our test suite which are definitely due to the recent xarray update (reverting to 0.10.9 solves the problem). The error is the famous (and very informative):
I have not been able to create a MWE yet, but it has something to do with read -> close -> append workflows on netcdf4 files (the error happens at the "append" step). Possibly multiprocessing also plays a role, but I can't be sure yet. I will try to find a way to reproduce this with a simple example, but this might take a while... |
{
"url": "https://api.github.com/repos/pydata/xarray/issues/2551/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
completed | 13221727 | issue |