issue_comments

Table actions

1 row where issue = 996352280 and user = 35968931 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

  • TomNicholas · 1 ✖

issue 1

  • Single matplotlib import · 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
921868793 https://github.com/pydata/xarray/pull/5794#issuecomment-921868793 https://api.github.com/repos/pydata/xarray/issues/5794 IC_kwDOAMm_X8428pn5 TomNicholas 35968931 2021-09-17T15:03:05Z 2021-09-17T15:03:05Z MEMBER

The slowest run took 11.40 times longer than the fastest. This could mean that an intermediate result is being cached.

What happens if you manually time just a single import (I think you can tell timeit to run only once)? It seems like averaging might not be giving an accurate reflection of the import time here.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Single matplotlib import 996352280

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