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/1759#issuecomment-349763381,https://api.github.com/repos/pydata/xarray/issues/1759,349763381,MDEyOklzc3VlQ29tbWVudDM0OTc2MzM4MQ==,5635139,2017-12-06T20:24:08Z,2017-12-06T20:24:08Z,MEMBER,"> our own assert_eq functions that both invoke the single-threaded scheduler, and also do a variety of other sanity checks like ensuring that the expected and computed dtypes and shapes are the same, that the keynames in graphs are sensible, etc..

What do you think about using that in our tests, i.e. `from dask.utils import asset_eq as assert_dask_equals`?

Or we could even check for a dask object in our own `assert_equals` and pass off to dask's?","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,279161550