issue_comments

Table actions

1 row where author_association = "MEMBER", issue = 802400938 and user = 14808389 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: updated_at (date)

user 1

  • keewis · 1 ✖

issue 1

  • fix da.pad example for numpy 1.20 · 1 ✖

author_association 1

  • MEMBER · 1 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
774548429 https://github.com/pydata/xarray/pull/4865#issuecomment-774548429 https://api.github.com/repos/pydata/xarray/issues/4865 MDEyOklzc3VlQ29tbWVudDc3NDU0ODQyOQ== keewis 14808389 2021-02-06T21:44:49Z 2021-02-06T21:48:36Z MEMBER

not sure. I would probably try to either check the new behavior of numpy with an example, or just copy the doctest into a test.

Edit: it would probably be good to merge this as soon as possible, all PRs fail because of this.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   fix da.pad example for numpy 1.20 802400938

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