issue_comments

Table actions

1 row where issue = 568705055 and user = 13770365 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

  • ngreenwald · 1 ✖

issue 1

  • open_dataarray(cache=False) still uses cached version of dataarray · 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
592051771 https://github.com/pydata/xarray/issues/3785#issuecomment-592051771 https://api.github.com/repos/pydata/xarray/issues/3785 MDEyOklzc3VlQ29tbWVudDU5MjA1MTc3MQ== ngreenwald 13770365 2020-02-27T16:30:36Z 2020-02-27T16:30:36Z NONE

Hey all, just wanted to follow up to see if anyone had suggestions for how to approach this.

We're running into this issue when we load an xarray, make some changes to it, and then save the modified version. Especially for interactive sessions, this produces bugs that are challenging to track down, as it appears that the previous step has failed, not that the actual loading is the problem. 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   open_dataarray(cache=False) still uses cached version of dataarray 568705055

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