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/5449#issuecomment-856285749,https://api.github.com/repos/pydata/xarray/issues/5449,856285749,MDEyOklzc3VlQ29tbWVudDg1NjI4NTc0OQ==,3309802,2021-06-07T21:45:30Z,2021-06-07T21:45:30Z,NONE,"@mathause sorry for breaking things here. Note that passing `output_dtypes` [didn't work as it was supposed to before](https://github.com/dask/dask/pull/7669#discussion_r634811360), and also didn't cause a cast. [We went back and forth](https://github.com/dask/dask/pull/7669#issuecomment-849074257) on whether `output_types` should cause explicit casting, and whether it was sensible to provide both it and `meta`. Ultimately we decided they should be mutually exclusive, and should not cause casting, but without much knowledge of how downstream libraries were using these arguments. So maybe we should revisit that choice in dask?

Also I think maybe this test should be changed rather than skipped. Saying `output_dtypes=[int]` and then `assert float == actual.dtype` just seems weird to me. Perhaps removing one of `output_dtypes` or `meta` from the test would be the best solution.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,913830070