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/3921#issuecomment-1498756227,https://api.github.com/repos/pydata/xarray/issues/3921,1498756227,IC_kwDOAMm_X85ZVTSD,14808389,2023-04-06T09:25:44Z,2023-04-06T09:25:58Z,MEMBER,"I think we'd need to be able to remove this `xfail` first: https://github.com/pydata/xarray/blob/f8127fc9ad24fe8b41cce9f891ab2c98eb2c679a/xarray/tests/test_backends.py#L712-L714 I didn't check, this could be `xpass`ing right now.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,590630281
https://github.com/pydata/xarray/issues/3921#issuecomment-606573918,https://api.github.com/repos/pydata/xarray/issues/3921,606573918,MDEyOklzc3VlQ29tbWVudDYwNjU3MzkxOA==,14808389,2020-03-31T11:38:20Z,2020-03-31T11:54:00Z,MEMBER,"I think the lock is used to synchronize the I/O on the `rasterio` file, so we can't really remove it. The failing test states it is a regression test for #2121, but since then the backend code was rewritten. We'd probably need a serializable lock that does not depend on dask (I don't know much about the backend code, though)

Edit: we could vendor `dask`'s `SerializableLock`, which basically wraps a `threading.Lock` but also makes sure to use the same lock after every pickle dumps/loads cycle.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,590630281