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/5526#issuecomment-1003391064,https://api.github.com/repos/pydata/xarray/issues/5526,1003391064,IC_kwDOAMm_X847zohY,1053153,2021-12-31T14:36:26Z,2021-12-31T14:36:26Z,CONTRIBUTOR,Is this change still of potential value?,"{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,929518413
https://github.com/pydata/xarray/pull/5526#issuecomment-870868874,https://api.github.com/repos/pydata/xarray/issues/5526,870868874,MDEyOklzc3VlQ29tbWVudDg3MDg2ODg3NA==,1053153,2021-06-29T19:48:48Z,2021-06-29T19:48:48Z,CONTRIBUTOR,"In my original PR, I wrote:

> In putting this together, I noted that open_zarr to re-read the data triggers this bug, while open_dataset(..., engine='zarr') does not. I'm not sure if my proposed fix is a band-aid, or if something in open_zarr is the real culprit.

I just want to be sure we think this is the correct fix, and there won't be any unintended consequences.  I'm really not familiar with the interaction of chunks between zarr, dask, and xarray.  I don't feel 100% sure this is the correct solution, though it fixes the immediate solution.","{""total_count"": 1, ""+1"": 1, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,929518413
https://github.com/pydata/xarray/pull/5526#issuecomment-867876696,https://api.github.com/repos/pydata/xarray/issues/5526,867876696,MDEyOklzc3VlQ29tbWVudDg2Nzg3NjY5Ng==,1053153,2021-06-24T18:54:23Z,2021-06-24T18:54:23Z,CONTRIBUTOR,"@jhamman Ready for review, though not urgent.

Mostly, I'm curious if this the right way to go about solving the linked issue, or if there is something deeper in xarray to update.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,929518413