Use `sync` pipeline entry points when available
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 80
- Forks
- 8
- Avg merge
- 21h 44m
- Merged PRs (30d)
- 5
Description
See https://github.com/zarr-developers/zarr-python/issues/3720 for more info, but we should implement {read,write}_sync once they have come online
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 by reading the linked zarr-developers/zarr-python issue 3720 and checking whether the sync pipeline entry points are available upstream. Then locate this project's pipeline integration and determine where {read,write}_sync would be connected. Done means both sync entry points are implemented once the upstream APIs exist.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100