issue_comments

Table actions

1 row where issue = 819003369 and user = 10194086 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

These facets timed out: author_association, issue

user 1

  • mathause · 1 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
802102704 https://github.com/pydata/xarray/pull/4977#issuecomment-802102704 https://api.github.com/repos/pydata/xarray/issues/4977 MDEyOklzc3VlQ29tbWVudDgwMjEwMjcwNA== mathause 10194086 2021-03-18T16:47:52Z 2021-03-18T16:48:14Z MEMBER

It looked pretty good when I reviewed it, so :+1:

Just quickly skimming the code it did not become entirely clear to me why this had to be after dask/dask#7234? You don't import sliding_window_view from dask. Also you re-define sliding_window_view in dask_array_compat.py - why don't you need this in dask proper? (Not complaining just wondering. Also feel free to not answer the question if you don't have time.)

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Use numpy & dask sliding_window_view for rolling 819003369

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