issue_comments
5 rows where issue = 96185559 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- segfault with hdf4 file · 5 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 123111762 | https://github.com/pydata/xarray/issues/484#issuecomment-123111762 | https://api.github.com/repos/pydata/xarray/issues/484 | MDEyOklzc3VlQ29tbWVudDEyMzExMTc2Mg== | rabernat 1197350 | 2015-07-21T00:45:23Z | 2015-07-21T00:45:23Z | MEMBER | I think I found the issue with netcdf.
gives the segfault. I'll take this issue to netcdf-python. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
segfault with hdf4 file 96185559 | |
| 123110874 | https://github.com/pydata/xarray/issues/484#issuecomment-123110874 | https://api.github.com/repos/pydata/xarray/issues/484 | MDEyOklzc3VlQ29tbWVudDEyMzExMDg3NA== | rabernat 1197350 | 2015-07-21T00:41:07Z | 2015-07-21T00:41:15Z | MEMBER | decode_cf=False doesn't help. Still segfaults on open_dataset |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
segfault with hdf4 file 96185559 | |
| 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 |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
segfault with hdf4 file 96185559 | |
| 123107777 | https://github.com/pydata/xarray/issues/484#issuecomment-123107777 | https://api.github.com/repos/pydata/xarray/issues/484 | MDEyOklzc3VlQ29tbWVudDEyMzEwNzc3Nw== | rabernat 1197350 | 2015-07-21T00:28:51Z | 2015-07-21T00:28:51Z | MEMBER | A stack trace shows that these were the last few functions called
So I guess that narrows it down a bit. |
{
"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
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]);
user 2