issue_comments

Table actions

2 rows where issue = 1643132089 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date), updated_at (date)

user 2

issue 1

  • [skip-ci] Add compute to groupby benchmarks · 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
1488832702 https://github.com/pydata/xarray/pull/7690#issuecomment-1488832702 https://api.github.com/repos/pydata/xarray/issues/7690 IC_kwDOAMm_X85Yvci- dcherian 2448579 2023-03-29T15:21:04Z 2023-03-29T15:21:04Z MEMBER

it runs the new benchmark on both main and HEAD so it should work as long as there is no error in the benchmarks

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   [skip-ci] Add compute to groupby benchmarks 1643132089
1486221550 https://github.com/pydata/xarray/pull/7690#issuecomment-1486221550 https://api.github.com/repos/pydata/xarray/issues/7690 IC_kwDOAMm_X85YlfDu Illviljan 14371165 2023-03-28T05:04:50Z 2023-03-28T05:04:50Z MEMBER

How come the benchmarks is not failing? Shouldn't it be significantly slower now?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   [skip-ci] Add compute to groupby benchmarks 1643132089

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