issue_comments
1 row where author_association = "MEMBER", issue = 291103680 and user = 1217238 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
These facets timed out: author_association
issue 1
- bug: 2D pcolormesh plots are wrong when coordinate is not ascending order · 1 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
360284640 | https://github.com/pydata/xarray/issues/1852#issuecomment-360284640 | https://api.github.com/repos/pydata/xarray/issues/1852 | MDEyOklzc3VlQ29tbWVudDM2MDI4NDY0MA== | shoyer 1217238 | 2018-01-24T21:47:22Z | 2018-01-24T21:47:22Z | MEMBER | One indication that something is broken here is that I can see use cases for plotting scrambled data, but for those cases I would probably defer to Rather than automatically sorting data, we could start raising an error if labels are unsorted. The error message could suggest either sorting the data with the |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
bug: 2D pcolormesh plots are wrong when coordinate is not ascending order 291103680 |
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