issue_comments
2 rows where issue = 503562032 and user = 1217238 sorted by updated_at descending
This data as json, CSV (advanced)
These facets timed out: author_association, issue
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
540928701 | https://github.com/pydata/xarray/issues/3377#issuecomment-540928701 | https://api.github.com/repos/pydata/xarray/issues/3377 | MDEyOklzc3VlQ29tbWVudDU0MDkyODcwMQ== | shoyer 1217238 | 2019-10-11T06:25:08Z | 2019-10-11T06:25:08Z | MEMBER | @jbusecke kudos to you for catching this so early, before we even made a release! https://github.com/pydata/xarray/pull/3393 should fix the immediate issue, though it's a pretty awkward fix. |
{ "total_count": 1, "+1": 0, "-1": 0, "laugh": 1, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Changed behavior for replacing coordinates on dataset. 503562032 | |
540917530 | https://github.com/pydata/xarray/issues/3377#issuecomment-540917530 | https://api.github.com/repos/pydata/xarray/issues/3377 | MDEyOklzc3VlQ29tbWVudDU0MDkxNzUzMA== | shoyer 1217238 | 2019-10-11T05:45:43Z | 2019-10-11T05:45:43Z | MEMBER | Yes, it was definitely my explicit indexes refactor. Apparently this wasn't tested? Here's a simpler reproduction:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Changed behavior for replacing coordinates on dataset. 503562032 |
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