issue_comments

Table actions

1 row where issue = 217584777 and user = 10050469 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

  • fmaussion · 1 ✖

issue 1

  • `cumsum` providing correct behavior for non-coordinate DataArrays? · 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
289806577 https://github.com/pydata/xarray/issues/1335#issuecomment-289806577 https://api.github.com/repos/pydata/xarray/issues/1335 MDEyOklzc3VlQ29tbWVudDI4OTgwNjU3Nw== fmaussion 10050469 2017-03-28T15:24:58Z 2017-03-28T15:24:58Z MEMBER

I'm not sure that whether coordinates should play a role here, but rather the dimensionality of the data (i.e. maybe xarray could infer that the data has one dimension and work on that axis?).

I personally find the numpy behavior with ndarrays (flattening the array before applying cumsum) quite dangerous, I would rather like it to raise an error...

python a = np.arange(12).reshape((4, 3)) np.cumsum(a) array([ 0, 1, 3, 6, 10, 15, 21, 28, 36, 45, 55, 66])

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   `cumsum` providing correct behavior for non-coordinate DataArrays? 217584777

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