issue_comments

Table actions

2 rows where issue = 274308380 and user = 6815844 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: updated_at (date)

These facets timed out: issue

user 1

  • fujiisoup · 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
345157498 https://github.com/pydata/xarray/issues/1720#issuecomment-345157498 https://api.github.com/repos/pydata/xarray/issues/1720 MDEyOklzc3VlQ29tbWVudDM0NTE1NzQ5OA== fujiisoup 6815844 2017-11-17T06:32:14Z 2017-11-17T06:32:14Z MEMBER

OK. Found a bug and sent a PR. This was the smallest bug fix I have ever done :)

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Possible regression with PyNIO data not being lazily loaded 274308380
345126212 https://github.com/pydata/xarray/issues/1720#issuecomment-345126212 https://api.github.com/repos/pydata/xarray/issues/1720 MDEyOklzc3VlQ29tbWVudDM0NTEyNjIxMg== fujiisoup 6815844 2017-11-17T02:23:09Z 2017-11-17T02:23:59Z MEMBER

I don't think we have tests of this case for any backend other than dask after #1532. In my local tests, many backend array are loaded after print.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Possible regression with PyNIO data not being lazily loaded 274308380

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