issue_comments

Table actions

1 row where author_association = "MEMBER", issue = 146908323 and user = 1217238 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

user 1

  • shoyer · 1 ✖

issue 1

  • datetime units interpretation wrong in special cases · 1 ✖

author_association 1

  • MEMBER · 1 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
207554987 https://github.com/pydata/xarray/issues/821#issuecomment-207554987 https://api.github.com/repos/pydata/xarray/issues/821 MDEyOklzc3VlQ29tbWVudDIwNzU1NDk4Nw== shoyer 1217238 2016-04-08T18:52:26Z 2016-04-08T18:52:26Z MEMBER

This may be related to https://github.com/pydata/xarray/issues/545

Likely this is due to numeric overflow of some sort in our datetime decoding function. This is the internal function that handles decoding dates if you're interested in digging into this: https://github.com/pydata/xarray/blob/v0.7.2/xarray/conventions.py#L115

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   datetime units interpretation wrong in special cases 146908323

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