-
Notifications
You must be signed in to change notification settings - Fork 0
Fixes #1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fixes #1
Conversation
…es by default in zarr
… to be written to zarr
…into dtree-zarrv3-2
…r's fill_value in assertion
@@ -1047,7 +1047,7 @@ def store( | |||
kwargs = {} | |||
if _zarr_v3(): | |||
# https://github.com/zarr-developers/zarr-python/pull/2113#issuecomment-2386718323 | |||
kwargs["path"] = self.zarr_group.name.lstrip("/") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FYI @TomAugspurger @jhamman and I are 95% sure that this line was unnecessary and a bug. It was causing consolidated metadata to not be written at the store root each time, and now that we changed it, it fixed various buggy behaviour we were seeing.
relevant to zarr-developers/zarr-python#2113 (comment)
I couldn't work out how to get the permissions right so I've just opened this against your PR branch @aladinor. I plan to make some more changes tomorrow.