issue_comments

Table actions

1 row where author_association = "MEMBER", issue = 913830070 and user = 5821660 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

  • kmuehlbauer · 1 ✖

issue 1

  • fix dask meta and output_dtypes error · 1 ✖

author_association 1

  • MEMBER · 1 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
856543812 https://github.com/pydata/xarray/pull/5449#issuecomment-856543812 https://api.github.com/repos/pydata/xarray/issues/5449 MDEyOklzc3VlQ29tbWVudDg1NjU0MzgxMg== kmuehlbauer 5821660 2021-06-08T07:51:49Z 2021-06-08T07:51:49Z MEMBER

Thanks for the ping @dcherian.

There is this test: https://github.com/pydata/xarray/blob/da0489f4c7c823915dbb52b681b867baa16bc6e3/xarray/tests/test_computation.py#L1314-L1330 which provides dtype in meta. Maybe these different tests have to be aligned/combined? Unfortunately memory gets hazy over time, so I can't say much more about it without a deeper dive into.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   fix dask meta and output_dtypes error 913830070

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