issue_comments

Table actions

1 row where issue = 255997962 and user = 2443309 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

user 1

  • jhamman · 1 ✖

issue 1

  • exit code 137 when using xarray.open_mfdataset · 1 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
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

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]);