issue_comments

Table actions

1 row where issue = 719881097 and user = 5635139 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

  • max-sixty · 1 ✖

issue 1

  • Decoding year 1 time · 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
707866819 https://github.com/pydata/xarray/pull/4506#issuecomment-707866819 https://api.github.com/repos/pydata/xarray/issues/4506 MDEyOklzc3VlQ29tbWVudDcwNzg2NjgxOQ== max-sixty 5635139 2020-10-13T16:39:03Z 2020-10-13T16:39:03Z MEMBER

Hi @znicholls — thanks for your PR, and welcome to xarray!

We've had a recent issue with an upstream change, so that is likely the cause of the error.

The PR LGTM, though I'll let those who know this area of the code better review it.

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Decoding year 1 time 719881097

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