ome-zarr-py labels logging still appears
Open
Beginner friendly
Nobody has claimed this yet.
needs: triage
priority: low
- Dominant language
- Python
- Stars
- 394
- Forks
- 95
- Avg merge
- 4d 3h
- Merged PRs (30d)
- 7
Description
This log:
no parent found for <ome_zarr.reader.Label object at 0x2a2c3d5a0>: None
which appears when reading labels from Zarr should have been disabled by the code in io_zarr.py, but somehow these logs still appear. It is confusing from the users because it seems that there is a problem when it's actually all ok. We should re-disable it.
Contributor guide
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 in io_zarr.py and trace the label-reading path for Zarr data, focusing on where the 'no parent found' log is emitted or suppressed. Reproduce reading labels from Zarr and confirm that the confusing log no longer appears while otherwise-valid reads continue to work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 78/100