issue_comments

Table actions

1 row where author_association = "NONE" and issue = 514792972 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

  • warn when updating coord.values : indexes are not updated · 1 ✖

author_association 1

  • NONE · 1 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
548272942 https://github.com/pydata/xarray/issues/3470#issuecomment-548272942 https://api.github.com/repos/pydata/xarray/issues/3470 MDEyOklzc3VlQ29tbWVudDU0ODI3Mjk0Mg== folmerkrikken 35295222 2019-10-31T08:58:10Z 2019-10-31T08:58:10Z NONE

@dcherian Yes, ds.assign_coords does work and that's what I'm using now.

So can ds.assign_coords(..) be seen as the right way and changing the values inplace with ds.time.values = pd.... the wrong way? It all worked fine until changing from version 0.11.3 to 0.12.0. 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   warn when updating coord.values : indexes are not updated 514792972

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