issue_comments
1 row where issue = 825079209 and user = 3460034 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- trouble slicing on sub-minute dataset · 1 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
793204639 | https://github.com/pydata/xarray/issues/5012#issuecomment-793204639 | https://api.github.com/repos/pydata/xarray/issues/5012 | MDEyOklzc3VlQ29tbWVudDc5MzIwNDYzOQ== | jthielen 3460034 | 2021-03-09T00:38:37Z | 2021-03-09T00:39:02Z | CONTRIBUTOR | I'll leave the exact issue up to someone more acquainted with string and slice handling on 1) Using pandas
However, notice that jump in the time coordinate...which leads to 2) In the failing example, the time coordinate is non-monotonic. If we
(the working example also has a monotonic time coordinate) And so, I would guess this is an example of string-based timedelta selection failing on non-monotonic coordinates. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
trouble slicing on sub-minute dataset 825079209 |
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