issue_comments

Table actions

1 row where issue = 1043378880 and user = 14808389 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

  • keewis · 1 ✖

issue 1

  • fix the detection of backend entrypoints · 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
958995873 https://github.com/pydata/xarray/pull/5931#issuecomment-958995873 https://api.github.com/repos/pydata/xarray/issues/5931 IC_kwDOAMm_X845KR2h keewis 14808389 2021-11-03T12:42:35Z 2021-11-03T12:54:10Z MEMBER

the only way I can think of is to somehow install a test package providing an entrypoint, check that it's in the list of detected engines and remove it again. However, installing within the test suite is fragile so we might have to monkeypatch something within importlib.metadata to have the same effect – wrap entry_points to add the test, maybe?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   fix the detection of backend entrypoints 1043378880

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