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/pull/1676#issuecomment-341999483,https://api.github.com/repos/pydata/xarray/issues/1676,341999483,MDEyOklzc3VlQ29tbWVudDM0MTk5OTQ4Mw==,10050469,2017-11-05T19:46:06Z,2017-11-05T19:46:06Z,MEMBER,"> Is there any need to add indexing tests for rasterio backend, after this issue #1429 is resolved?

No, I don't think so. Thanks!","{""total_count"": 1, ""+1"": 1, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,269996138
https://github.com/pydata/xarray/pull/1676#issuecomment-341370145,https://api.github.com/repos/pydata/xarray/issues/1676,341370145,MDEyOklzc3VlQ29tbWVudDM0MTM3MDE0NQ==,10050469,2017-11-02T09:52:22Z,2017-11-02T11:00:22Z,MEMBER,">  @fmaussion How did you notice issue #1429?
> I found test_backends.py already checked the orthogonal indexing.
> I guess there are some untested use cases.

I don't remember exactly, but it happened when I wrote tests for rasterio's indexing: https://github.com/pydata/xarray/blob/master/xarray/tests/test_backends.py#L1855-L1884 (I just tested all possible combinations of index operations I could think of). 

The caching mechanism has some non-intuitive consequences, for example that some indexing operations not allowed on a rasterio file stored on disk become available once the data is cached:  https://github.com/pydata/xarray/blob/master/xarray/tests/test_backends.py#L1916-L1927","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,269996138