issue_comments: 123092900
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/484#issuecomment-123092900 | https://api.github.com/repos/pydata/xarray/issues/484 | 123092900 | MDEyOklzc3VlQ29tbWVudDEyMzA5MjkwMA== | 1217238 | 2015-07-20T23:35:03Z | 2015-07-20T23:35:03Z | MEMBER | xray is using netCDF4-python here internally, so I'm surprised the behavior differs. I have not tested reading hdf4 files myself yet, but if netCDF4-python can handle them then we should be able to, as well. One possible difference is that xray reads lots of metadata when it opens a file, whereas netCDF4-python just opens the file. It's possible that the segfault is triggered by one of these actions, e.g., reading the variable attributes. My guess is that this is a upstream bug or build issue with the netCDF packages. However, tracking it down may be easier said than done. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
96185559 |