issue_comments
2 rows where issue = 94030797 and user = 1217238 sorted by updated_at descending
This data as json, CSV (advanced)
issue 1
- groupby / apply and dask (`open_mfdataset`) · 2 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
121432005 | https://github.com/pydata/xarray/issues/458#issuecomment-121432005 | https://api.github.com/repos/pydata/xarray/issues/458 | MDEyOklzc3VlQ29tbWVudDEyMTQzMjAwNQ== | shoyer 1217238 | 2015-07-15T00:02:33Z | 2015-07-15T00:02:33Z | MEMBER | This was https://github.com/ContinuumIO/dask/issues/391, which has now been fixed upstream in dask. Thanks @mrocklin! |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
groupby / apply and dask (`open_mfdataset`) 94030797 | |
120064381 | https://github.com/pydata/xarray/issues/458#issuecomment-120064381 | https://api.github.com/repos/pydata/xarray/issues/458 | MDEyOklzc3VlQ29tbWVudDEyMDA2NDM4MQ== | shoyer 1217238 | 2015-07-09T16:40:43Z | 2015-07-09T16:40:43Z | MEMBER | This is definitely a dask.array bug... I'll track down the details later. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
groupby / apply and dask (`open_mfdataset`) 94030797 |
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 1