follow-up issues in `zarr-python`
MSanKeys963 opened this issue · 2 comments
MSanKeys963 commented
Linking this from #54. Conversations on some issues have gone stale. Here are issues in zarr-python
that need follow-up from the author, and then we can decide the best action to take:
- zarr-developers/zarr-python#1035
- zarr-developers/zarr-python#991
- zarr-developers/zarr-python#1029
- zarr-developers/zarr-python#1017
- zarr-developers/zarr-python#1104
- zarr-developers/zarr-python#962
- zarr-developers/zarr-python#904
- zarr-developers/zarr-python#868
- zarr-developers/zarr-python#864
- zarr-developers/zarr-python#784
- zarr-developers/zarr-python#777
- zarr-developers/zarr-python#776
- zarr-developers/zarr-python#809
If you think this is in the right category, feel free to follow up on the issue. Thanks!
joshmoore commented
-
to-be-reproduced / needs-unit-test (new label)
-
yes, just check in
- 991
- 1029
- 868 (possibly reproduce)
- 864
- 777
-
maybe close (these are trickier)
- 1017 (docs, help?)
- 962 (after asking for comments?) possibly a documentation issue
- 784 (synchronization is often a tricky one)
-
help wanted / good first
- 904
-
needs a review or first comment
- 776 (suggest a PR?)
joshmoore commented
Updated my comment for all the issues listed here, @MSanKeys963.