issue_comments

Table actions

2 rows where issue = 96185559 and user = 1217238 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date), updated_at (date)

user 1

  • shoyer · 2 ✖

issue 1

  • segfault with hdf4 file · 2 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
123108405 https://github.com/pydata/xarray/issues/484#issuecomment-123108405 https://api.github.com/repos/pydata/xarray/issues/484 MDEyOklzc3VlQ29tbWVudDEyMzEwODQwNQ== shoyer 1217238 2015-07-21T00:30:28Z 2015-07-21T00:30:28Z MEMBER

You could try loading the dataset with decode_cf=False in open_dataset. That might delay the segfault until later.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   segfault with hdf4 file 96185559
123092900 https://github.com/pydata/xarray/issues/484#issuecomment-123092900 https://api.github.com/repos/pydata/xarray/issues/484 MDEyOklzc3VlQ29tbWVudDEyMzA5MjkwMA== shoyer 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
}
   segfault with hdf4 file 96185559

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

CREATE TABLE [issue_comments] (
   [html_url] TEXT,
   [issue_url] TEXT,
   [id] INTEGER PRIMARY KEY,
   [node_id] TEXT,
   [user] INTEGER REFERENCES [users]([id]),
   [created_at] TEXT,
   [updated_at] TEXT,
   [author_association] TEXT,
   [body] TEXT,
   [reactions] TEXT,
   [performed_via_github_app] TEXT,
   [issue] INTEGER REFERENCES [issues]([id])
);
CREATE INDEX [idx_issue_comments_issue]
    ON [issue_comments] ([issue]);
CREATE INDEX [idx_issue_comments_user]
    ON [issue_comments] ([user]);