Skip to content

Restrict ome-zarr version range in meta.yaml#33

Merged
jdblischak merged 2 commits intoconda-forge:mainfrom
nilchia:main
Mar 20, 2026
Merged

Restrict ome-zarr version range in meta.yaml#33
jdblischak merged 2 commits intoconda-forge:mainfrom
nilchia:main

Conversation

@nilchia
Copy link
Contributor

@nilchia nilchia commented Mar 13, 2026

Checklist

  • Used a personal fork of the feedstock to propose changes
  • Bumped the build number (if the version is unchanged)
  • Reset the build number to 0 (if the version changed)
  • Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
  • Ensured the license file is being packaged.

Spatialdata does not work with the latest ome-zarr version 0.14.0.

It fails with this error:

  File "/usr/local/lib/python3.12/site-packages/zarr/core/common.py", line 200, in parse_shapelike
    raise TypeError(msg)
TypeError: Expected an iterable of integers. Got ((1, 1, 1), (100,), (100,)) instead.

or

  File "/usr/local/lib/python3.12/site-packages/zarr/core/common.py", line 200, in parse_shapelike
    raise TypeError(msg)
TypeError: Expected an iterable of integers. Got ((3,), (256, 256, 256, 256, 256, 256, 256, 256, 256, 256, 256, 184), (256, 256, 256, 256, 256, 256, 256, 256, 256, 256, 256, 184)) instead.
.

@pavanvidem found it when we were testing the spatialdata wrapper on Galaxy. (here)

@conda-forge-admin
Copy link
Contributor

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

Copy link
Member

@jdblischak jdblischak left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This will require a repodata patch as well. I can submit that once the other maintainers approve and merge this PR.

Some thoughts:

  1. Can we add a simple test that would catch this incompatibility if it arises in the future?
  2. Has this been reported upstream in the spatialdata and/or ome-zarr repositories?

@nilchia
Copy link
Contributor Author

nilchia commented Mar 13, 2026

@jdblischak thanks.

The ome-zarr update was made 2 days ago.
I checked spatialdata and there is already two reported issues for that:
scverse/spatialdata#1090
scverse/spatialdata#1091

@jdblischak
Copy link
Member

@LucaMarconato please review

@LucaMarconato
Copy link
Member

LGTM thanks! I'm working on merging a fix for it, that will be included in the next release (scverse/spatialdata#1092). But until then this patch will fix the install.

@jdblischak jdblischak merged commit 9996bed into conda-forge:main Mar 20, 2026
4 checks passed
@jdblischak
Copy link
Member

I submitted a repodata patch in conda-forge/conda-forge-repodata-patches-feedstock#1176. Please review/approve

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.

4 participants