issue_comments

Table actions

1 row where issue = 1519058102 and user = 950575 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

  • ocefpaf · 1 ✖

issue 1

  • install `numbagg` from `conda-forge` · 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
1371028352 https://github.com/pydata/xarray/pull/7415#issuecomment-1371028352 https://api.github.com/repos/pydata/xarray/issues/7415 IC_kwDOAMm_X85RuDuA ocefpaf 950575 2023-01-04T14:53:15Z 2023-01-04T14:53:15Z CONTRIBUTOR

that looks like it works, besides the fact that conda reports numbagg=0.2.1 but

It is not a conda problem but a bug upstream. The v0.2.1 tag hasv0.2.0 hardcoded in it.

See https://github.com/numbagg/numbagg/blob/v0.2.1/setup.py#L24

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   install `numbagg` from `conda-forge` 1519058102

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