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/593#issuecomment-144270497,https://api.github.com/repos/pydata/xarray/issues/593,144270497,MDEyOklzc3VlQ29tbWVudDE0NDI3MDQ5Nw==,1217238,2015-09-30T03:18:15Z,2015-09-30T03:18:15Z,MEMBER,"I'm all behind that error message in principle, but it needs to be specific to the netcdf4 backend. For example, this works perfectly fine with scipy. Given these constraints, especially given that either of these arrays may be triggered lazily by a dask.array, I think this will be difficult to solve at all times when the expression is written.
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,108769226
https://github.com/pydata/xarray/issues/593#issuecomment-144133156,https://api.github.com/repos/pydata/xarray/issues/593,144133156,MDEyOklzc3VlQ29tbWVudDE0NDEzMzE1Ng==,1217238,2015-09-29T17:46:04Z,2015-09-29T17:46:04Z,MEMBER,"My vote would be for catching and re-raising the error with a more informative message. Something like:

```
IndexError: the indexing operation you are attempting to perform is not
valid on netCDF4.Variable object. Try loading your data into memory
first by calling .load().

Original traceback:
...
```

This is automatic when you re-raise on Python 3. On Python 2, you'll have to use `traceback.format_exc()` to capture the traceback.
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,108769226
https://github.com/pydata/xarray/issues/593#issuecomment-143914481,https://api.github.com/repos/pydata/xarray/issues/593,143914481,MDEyOklzc3VlQ29tbWVudDE0MzkxNDQ4MQ==,1217238,2015-09-29T01:01:39Z,2015-09-29T01:01:39Z,MEMBER,"We could work around this, but this is arguably a bug/limitation of netCDF4 Python, which no longer allows indexing with unsorted integer sequences. See https://github.com/Unidata/netcdf4-python/issues/300 and https://github.com/Unidata/netcdf4-python/pull/308.

I think this could probably be fixed upstream somewhat straightforwardly by canonicalizing indexers as integer arrays instead of as boolean arrays. I'm not sure what we can do about it here.
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,108769226