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/3215#issuecomment-521503585,https://api.github.com/repos/pydata/xarray/issues/3215,521503585,MDEyOklzc3VlQ29tbWVudDUyMTUwMzU4NQ==,1217238,2019-08-15T03:50:00Z,2019-08-15T03:50:00Z,MEMBER,"> I still don't understand the different code paths between `decode_cf=True` and `decode_cf=False` + explicit call to `xarray.decode_cf()`

In the first case, CF conventions decoding is done on xarray's internal lazy BackendArray objects.

In the second case, CF conventions decoding is done on dask arrays. There are a few cases where this can be slower / require loading more data to look at a small slice of array data.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,480512400
https://github.com/pydata/xarray/issues/3215#issuecomment-521500878,https://api.github.com/repos/pydata/xarray/issues/3215,521500878,MDEyOklzc3VlQ29tbWVudDUyMTUwMDg3OA==,1217238,2019-08-15T03:32:02Z,2019-08-15T03:32:02Z,MEMBER,A short term work around is to set the environment variable `NUMPY_EXPERIMENTAL_ARRAY_FUNCTION=0` before importing NumPy.,"{""total_count"": 2, ""+1"": 2, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,480512400
https://github.com/pydata/xarray/issues/3215#issuecomment-521492717,https://api.github.com/repos/pydata/xarray/issues/3215,521492717,MDEyOklzc3VlQ29tbWVudDUyMTQ5MjcxNw==,1217238,2019-08-15T02:40:10Z,2019-08-15T02:40:10Z,MEMBER,"This is definitely due to NumPy 1.17 / `__array_function__`, which means that `np.ravel` now calls out to a dask function rather than coercing to NumPy.

I think the right fix is to add explicit casting to NumPy, e.g., `np.ravel(np.asarray(array[indexer]))`","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,480512400