Repository navigation
Fix: do not include extra_metadata in zarr provenance dump - #4885
Merged
Merged
Conversation
h-mayorquin
approved these changes
Oct 20, 2026
h-mayorquin
left a comment
h-mayorquin
left a comment
Contributor
There was a problem hiding this comment.
LGTM
We should at some point route the timestamps through their own channel and I think that we can rid of the not-very-specific "extra metadata" entry for the sake of clarity.
chrishalcrow
approved these changes
Oct 21, 2026
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Similar to #4883, but for zarr provenance:
Since saving to zarr has its internal mechanism to store probe and timestampos info, we can safely drop these fields (extra metadata) from the provenance.
Also fixed a bug that prevented
include_extra_metadatato be recursively passed to children whento_dict(recursive=True)