issue_comments

Table actions

1 row where issue = 766979952 and user = 13301940 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

These facets timed out: issue

user 1

  • andersy005 · 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
744831125 https://github.com/pydata/xarray/pull/4694#issuecomment-744831125 https://api.github.com/repos/pydata/xarray/issues/4694 MDEyOklzc3VlQ29tbWVudDc0NDgzMTEyNQ== andersy005 13301940 2020-12-14T23:51:50Z 2020-12-14T23:51:50Z MEMBER

Nice! I think we get 2 hypter-threaded cores. So I can also try -n 4 and see if that helps. I wonder if there is any downside to this?

In the past, I've run into race conditions when using pytest-xdist for tests that required I/O tasks such as file downloading. So, it's likely everything will run fine with -n 4 provided we don't have tests with tasks that are likely to create race conditions. 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   CI: run tests in parallel (pytest-xdist) 766979952

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