id,node_id,number,title,user,state,locked,assignee,milestone,comments,created_at,updated_at,closed_at,author_association,active_lock_reason,draft,pull_request,body,reactions,performed_via_github_app,state_reason,repo,type 2267803218,PR_kwDOAMm_X85t8pSN,8980,Complete deprecation of Dataset.dims returning dict,35968931,open,0,,,6,2024-04-28T20:32:29Z,2024-05-01T15:40:44Z,,MEMBER,,0,pydata/xarray/pulls/8980," - [x] Completes deprecation cycle described in #8496, and started in #8500 - [ ] ~~Tests added~~ - [x] User visible changes (including notable bug fixes) are documented in `whats-new.rst` - [ ] ~~New functions/methods are listed in `api.rst`~~ ","{""url"": ""https://api.github.com/repos/pydata/xarray/issues/8980/reactions"", ""total_count"": 1, ""+1"": 1, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,,13221727,pull 2120030667,PR_kwDOAMm_X85mGm4g,8712,Only use CopyOnWriteArray wrapper on BackendArrays,35968931,open,0,,,6,2024-02-06T06:05:53Z,2024-02-07T17:09:56Z,,MEMBER,,0,pydata/xarray/pulls/8712,"This makes sure we only use the `CopyOnWriteArray` wrapper on arrays that have been explicitly marked to be lazily-loaded (through being subclasses of `BackendArray`). Without this change we are implicitly assuming that any array type obtained through the BackendEntrypoint system should be treated as if it points to an on-disk array. Motivated by https://github.com/pydata/xarray/issues/8699, which is a counterexample to that assumption. - [ ] Closes #xxxx - [ ] Tests added - [ ] User visible changes (including notable bug fixes) are documented in `whats-new.rst` - [ ] New functions/methods are listed in `api.rst` ","{""url"": ""https://api.github.com/repos/pydata/xarray/issues/8712/reactions"", ""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,,13221727,pull