issue_comments
3 rows where issue = 255997962 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- exit code 137 when using xarray.open_mfdataset · 3 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 329181674 | https://github.com/pydata/xarray/issues/1561#issuecomment-329181674 | https://api.github.com/repos/pydata/xarray/issues/1561 | MDEyOklzc3VlQ29tbWVudDMyOTE4MTY3NA== | jamesstidard 1797906 | 2017-09-13T14:16:06Z | 2017-09-13T14:16:06Z | NONE | Increasing the chunk sizes seemed to resolve this issue. I was loading readings over time on the world as 360x180xT was tryin to rechunk them to 1x1xT. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
exit code 137 when using xarray.open_mfdataset 255997962 | |
| 328400296 | https://github.com/pydata/xarray/issues/1561#issuecomment-328400296 | https://api.github.com/repos/pydata/xarray/issues/1561 | MDEyOklzc3VlQ29tbWVudDMyODQwMDI5Ng== | shoyer 1217238 | 2017-09-11T02:33:51Z | 2017-09-11T02:33:51Z | MEMBER | Running out of memory seems like the most likely culprit to me, at least if you're running a recent version of xarray (we used to have some issues with insufficient locking when reading HDF5 files). Try opening a smaller number of files to see if that gives any clues. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
exit code 137 when using xarray.open_mfdataset 255997962 | |
| 328191120 | https://github.com/pydata/xarray/issues/1561#issuecomment-328191120 | https://api.github.com/repos/pydata/xarray/issues/1561 | MDEyOklzc3VlQ29tbWVudDMyODE5MTEyMA== | jhamman 2443309 | 2017-09-08T19:17:45Z | 2017-09-08T19:17:45Z | MEMBER | @jamesstidard - Can you provide something closer to a "minimum, complete, verifiable example". As it is, any number of things could be causing the problem you describe. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
exit code 137 when using xarray.open_mfdataset 255997962 |
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 3