Skip to content

merge: bring big int state protection into edit mode branch#125

Open
seankmartin wants to merge 4 commits intofeature/edit-modefrom
fix/anchor-segment-serialize
Open

merge: bring big int state protection into edit mode branch#125
seankmartin wants to merge 4 commits intofeature/edit-modefrom
fix/anchor-segment-serialize

Conversation

@seankmartin
Copy link
Copy Markdown

Should also fix the big int that is ending up in the state, but this will help protect against it

jbms and others added 4 commits March 21, 2026 13:02
…e#913)

Fixes google#905

Prior to google#876, any transform specified for an OME-zarr multiscale dataset
(and/or its base scale level) was handled internally and not exposed to users.

After google#876, the transform was exposed as the default coordinate transform
instead of being applied internally in all cases, which changed the meaning of
existing states with an explicitly-specified transform if the extracted
transform is not the identity transform.

This commit changes the behavior back to the pre-google#876 behavior for OME metadata
versions less than 0.6.  For OME metadata versions >= 0.6, the post-google#876
behavior remains.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants