CI breakage with new zarr
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 366
- Forks
- 96
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
xref: https://github.com/zarr-developers/VirtualiZarr/pull/677#issuecomment-3084297201
cc @d-v-b
We are seeing several test failures recently, presumably as a consequence of the dtype refactor in zarr.
Example output:
ValueError: No Zarr data type found that matches {'name': '<i1', 'object_codec_id': None}
Other errors to do with missing variables are probably a direct consequence of this.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked VirtualiZarr pull request and the CI test failures that reproduce the reported Zarr dtype error. Trace the related missing-variable errors to determine whether they are consequences of the dtype refactor. Done means the affected tests pass with the new Zarr version and the CI failures are resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ci-cd, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100