issue_comments: 346056557
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/1732#issuecomment-346056557 | https://api.github.com/repos/pydata/xarray/issues/1732 | 346056557 | MDEyOklzc3VlQ29tbWVudDM0NjA1NjU1Nw== | 1197350 | 2017-11-21T15:12:28Z | 2017-11-21T15:12:38Z | MEMBER | Guillaume--this is very troubling! I use xarray frequently on ARGO netCDF files. It would be a shame if we broke something related to reading them. It sounds like this could be related to the indexing changes in #1676. Since rc1, xarray 0.10.0 has gone through another release candidate (rc2) and is now in full release. Can you try upgrading to the just-released 0.10.0 and verify whether the problem is still present? |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
275744315 |