issue_comments: 1254062705
This data as json
| 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/6475#issuecomment-1254062705 | https://api.github.com/repos/pydata/xarray/issues/6475 | 1254062705 | IC_kwDOAMm_X85Kv3px | 6528957 | 2022-09-21T18:15:26Z | 2022-10-29T02:45:24Z | CONTRIBUTOR | sorry about the long delay here. This has been updated for the V3 store paths used in Zarr >v2.12 and to remove the need for specifying To do: - [x] wait for zarr v2.13 release, hopefully also including a new fix in #https://github.com/zarr-developers/zarr-python/pull/1142 - [x] update at least one CI test case to run the tests with zarr v2.13 and ZARR_V3_EXPERIMENTAL_API=1 enviroment variable A separate issue is that consolidated metadata isn't in the core Zarr v3 spec, so we will need to have a Zarr Enhancement Proposal to formally define how the metadata should be stored. In the experimental API, it behaves as for v2 and is stored at |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
1200581329 |