issue_comments
1 row where author_association = "MEMBER", issue = 283345586 and user = 1217238 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Comparison with masked array yields object-array with nans for masked values · 1 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
354575001 | https://github.com/pydata/xarray/issues/1792#issuecomment-354575001 | https://api.github.com/repos/pydata/xarray/issues/1792 | MDEyOklzc3VlQ29tbWVudDM1NDU3NTAwMQ== | shoyer 1217238 | 2017-12-30T23:37:51Z | 2017-12-30T23:37:51Z | MEMBER | Yes, I suppose we can consider this a bug. The right behavior would be to convert the masked array into an xarray object before the operation, e.g.,
We currently don't have any masked array specific logic for arithmetic so this would require special case handling. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Comparison with masked array yields object-array with nans for masked values 283345586 |
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