You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Re-open the zarr group after da.compute() in _write_raster_datatree so that the main process picks up metadata written by ome-zarr-py's delayed write_multiscales_metadata() task, which runs in a subprocess under the 'processes' scheduler and leaves the original in-memory GroupMetadata stale. The fresh group is returned to _write_raster so the subsequent spatialdata attrs write also uses the correct on-disk state.
…sses scheduler (#1024)
Re-open the zarr group after da.compute() in _write_raster_datatree so
that the main process picks up metadata written by ome-zarr-py's delayed
write_multiscales_metadata() task, which runs in a subprocess under the
'processes' scheduler and leaves the original in-memory GroupMetadata stale.
The fresh group is returned to _write_raster so the subsequent spatialdata
attrs write also uses the correct on-disk state.
Upstream issue: ome/ome-zarr-py#580
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
The re-open after da.compute() was inheriting stale consolidated metadata,
which caused KeyError when newly written children (e.g. labels3d_multiscale_xarray)
were not yet reflected in it. Passing use_consolidated=False forces zarr to
read group membership directly from the store instead.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 91.93%. Comparing base (8d7f72f) to head (b12778d). ⚠️ Report is 26 commits behind head on main.
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
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.
Closes#1024
Re-open the zarr group after da.compute() in _write_raster_datatree so that the main process picks up metadata written by ome-zarr-py's delayed write_multiscales_metadata() task, which runs in a subprocess under the 'processes' scheduler and leaves the original in-memory GroupMetadata stale. The fresh group is returned to _write_raster so the subsequent spatialdata attrs write also uses the correct on-disk state.
Added tests.
Upstream issue: ome/ome-zarr-py#580