issue_comments

Table actions

1 row where issue = 178359375 and user = 1197350 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: updated_at (date)

user 1

  • rabernat · 1 ✖

issue 1

  • dask tokenize error with chunking · 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
248633542 https://github.com/pydata/xarray/issues/1014#issuecomment-248633542 https://api.github.com/repos/pydata/xarray/issues/1014 MDEyOklzc3VlQ29tbWVudDI0ODYzMzU0Mg== rabernat 1197350 2016-09-21T14:42:26Z 2016-09-21T14:42:26Z MEMBER

Update: the underlying data of the variable that was causing the error was a numpy.memmap. Tokenizing works with standard memmaps; however, this memmap was produced by adding together two other memmaps. The resuling object has a .filename attribute, but that attribute's values is None. I was able to overcome the issue by converting to a numpy array.

I think this is a problem with the way dask tokenizes memmaps, not with xarray. I will raise an issue on dask and close this issue.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   dask tokenize error with chunking 178359375

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