issue_comments

Table actions

2 rows where issue = 551344538 and user = 2448579 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

  • dcherian · 2 ✖

issue 1

  • Error using reduce(): percentile() got an unexpected keyword argument 'axis' · 2 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
575736943 https://github.com/pydata/xarray/issues/3701#issuecomment-575736943 https://api.github.com/repos/pydata/xarray/issues/3701 MDEyOklzc3VlQ29tbWVudDU3NTczNjk0Mw== dcherian 2448579 2020-01-17T18:15:26Z 2020-01-17T18:15:26Z MEMBER

yes. you'll need to have 1 chunk along the dimension being reduced (here 'time').

The reason is that there is no approximate quantile algorithm implemented in dask. So this implementation is just calling np.nanpercentile on each block of the array. If you're reducing along time, each block must have the entire time axis for this to work.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Error using reduce(): percentile() got an unexpected keyword argument 'axis' 551344538
575670529 https://github.com/pydata/xarray/issues/3701#issuecomment-575670529 https://api.github.com/repos/pydata/xarray/issues/3701 MDEyOklzc3VlQ29tbWVudDU3NTY3MDUyOQ== dcherian 2448579 2020-01-17T15:24:48Z 2020-01-17T15:24:48Z MEMBER

seems to make quantile work, but it might be a bad idea to monkeypatch. T

Personally I would add this quantile function and then do quantile(ds, q=0.99, dim="SOMETHING"). We should issue a release soon though.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Error using reduce(): percentile() got an unexpected keyword argument 'axis' 551344538

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