issue_comments

Table actions

1 row where issue = 400039356 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

issue 1

  • porting to new resample when how is lambda/function unclear, wrong advice given. · 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
454981881 https://github.com/pydata/xarray/issues/2685#issuecomment-454981881 https://api.github.com/repos/pydata/xarray/issues/2685 MDEyOklzc3VlQ29tbWVudDQ1NDk4MTg4MQ== max-sixty 5635139 2019-01-16T23:20:34Z 2019-01-16T23:20:34Z MEMBER

Thanks for the report @lexual . Agree that's unclear:

The error message should state that you use apply since it's a lambda; e.g.

```python

fn = lambda x: xr.DataArray(3) da.resample(time='QS-DEC').apply(fn)

Out[19]: <xarray.DataArray (time: 4)> array([3, 3, 3, 3]) Coordinates: * time (time) datetime64[ns] 1999-12-01 2000-03-01 2000-06-01 2000-09-01 ```

We'd take a PR to fix that, but fairly low priority given it's a deprecated feature

But the function also fails for fn = lambda values: 3 (and fn = lambda x: x.sum().item()); I think we could add something to handle a function that returns a number rather than an array

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   porting to new resample when how is lambda/function unclear, wrong advice given. 400039356

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