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/813#issuecomment-204161956,https://api.github.com/repos/pydata/xarray/issues/813,204161956,MDEyOklzc3VlQ29tbWVudDIwNDE2MTk1Ng==,1217238,2016-03-31T22:46:57Z,2016-03-31T22:47:31Z,MEMBER,"This looks like another dask.array bug (because it only turns up before data is loaded). CC @mrocklin @jcrist

xarray's squeeze just uses array indexing under the covers (e.g., `x.squeeze()` -> `x.data[..., 0, ...]` where you should replace `...` by an appropriate number of slices `:`). So the usual strategy would be to verify that squeezing one of these variables in dask gives the same error message (e.g., `ds['something'].data[..., 0, ...].compute()`), and then construct a failing test case for dask that doesn't rely on xarray by making an array with synthetic data with the same `dtype` and `chunks`.
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,144957100