issue_comments: 148784572
This data as json
html_url | issue_url | id | node_id | user | created_at | updated_at | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
https://github.com/pydata/xarray/issues/627#issuecomment-148784572 | https://api.github.com/repos/pydata/xarray/issues/627 | 148784572 | MDEyOklzc3VlQ29tbWVudDE0ODc4NDU3Mg== | 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 } |
111795064 |