issue_comments

Table actions

1 row where author_association = "MEMBER", issue = 800825901 and user = 6213168 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

  • crusaderky · 1 ✖

issue 1

  • ⚠️ Nightly upstream-dev CI failed ⚠️ · 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
774471403 https://github.com/pydata/xarray/issues/4860#issuecomment-774471403 https://api.github.com/repos/pydata/xarray/issues/4860 MDEyOklzc3VlQ29tbWVudDc3NDQ3MTQwMw== crusaderky 6213168 2021-02-06T12:38:11Z 2021-02-06T12:38:23Z MEMBER

@keewis looks like the xarray code is making assumptions on the dask internal implementation, instead of relying on the public interface alone. I'm on it; expect a fix very shortly.

 
{
    "total_count": 2,
    "+1": 2,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   ⚠️ Nightly upstream-dev CI failed ⚠️ 800825901

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