issue_comments

Table actions

1 row where issue = 1265366275 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

issue 1

  • exception groups · 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
1150517809 https://github.com/pydata/xarray/issues/6678#issuecomment-1150517809 https://api.github.com/repos/pydata/xarray/issues/6678 IC_kwDOAMm_X85Ek4Ix TomNicholas 35968931 2022-06-08T23:38:10Z 2022-06-08T23:38:10Z MEMBER

To expand on what was discussed in the dev call today: this feature is potentially useful any time we map a function over multiple variables, and the function could fail with separate errors for each variable. An ExceptionGroup allows us to raise every error together, showing the user everything that went wrong, rather than us having to raise one error (e.g. the first) and suppress the rest.

How would we feel about a dependency on the backport package though?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   exception groups 1265366275

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