issue_comments
2 rows where author_association = "MEMBER" and issue = 110726841 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- operations with pd.to_timedelta() now fails · 2 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
146988731 | https://github.com/pydata/xarray/issues/615#issuecomment-146988731 | https://api.github.com/repos/pydata/xarray/issues/615 | MDEyOklzc3VlQ29tbWVudDE0Njk4ODczMQ== | shoyer 1217238 | 2015-10-09T21:21:41Z | 2015-10-09T21:21:41Z | MEMBER |
The reason why this broke is that pandas used to return I agree that it would be nice to support this sort of conversion automatically. I opened a new issue for that (#616). |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
operations with pd.to_timedelta() now fails 110726841 | |
146975622 | https://github.com/pydata/xarray/issues/615#issuecomment-146975622 | https://api.github.com/repos/pydata/xarray/issues/615 | MDEyOklzc3VlQ29tbWVudDE0Njk3NTYyMg== | jhamman 2443309 | 2015-10-09T20:10:45Z | 2015-10-09T20:10:45Z | MEMBER | Do you have to use
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
operations with pd.to_timedelta() now fails 110726841 |
Advanced export
JSON shape: default, array, newline-delimited, object
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]);
user 2