issue_comments
1 row where author_association = "MEMBER", issue = 111795064 and user = 1217238 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- string coordinate gets converted to object coordinate upon addition of variable to dataset · 1 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
148784572 | https://github.com/pydata/xarray/issues/627#issuecomment-148784572 | https://api.github.com/repos/pydata/xarray/issues/627 | MDEyOklzc3VlQ29tbWVudDE0ODc4NDU3Mg== | shoyer 1217238 | 2015-10-16T17:51:56Z | 2015-10-16T17:51:56Z | MEMBER | Thanks for the report -- this does seem like a bug to me. We do end up converting from fixed width strings to object quite often (to get around limitations of NumPy's strings), but adding in a variable should not change the type of any existing variables. It's possible the best fix here will be to convert all string arrays into an object type as soon as they are loaded into xray objects. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
string coordinate gets converted to object coordinate upon addition of variable to dataset 111795064 |
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