issue_comments

Table actions

1 row where author_association = "NONE", issue = 440233667 and user = 4762711 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

  • zbarry · 1 ✖

issue 1

  • test_rolling_wrapped_dask is failing with dask-master · 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
504061610 https://github.com/pydata/xarray/issues/2940#issuecomment-504061610 https://api.github.com/repos/pydata/xarray/issues/2940 MDEyOklzc3VlQ29tbWVudDUwNDA2MTYxMA== zbarry 4762711 2019-06-20T15:03:22Z 2019-06-20T15:03:22Z NONE

@shoyer - yeah, I'd tend to agree. I had to do a bit of digging when I encountered this problem, because I was getting serialization errors (since it was doing away with the chunks on massive arrays) that I then eventually connected to this rolling problem. An explicit message that says "can't do this yet" would be good in light of this kind of situation.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   test_rolling_wrapped_dask is failing with dask-master 440233667

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