Unit tests failing (OK for now after pinning Zarr) #62

Activity

1. valeriupredoi

   added

   bugSomething isn't workingSomething isn't working

   testingtesting duhtesting duh

   on Mar 6, 2023
2. valeriupredoi

   self-assigned this

   on Mar 6, 2023
3. valeriupredoi commented on Mar 6, 2023

   

   valeriupredoi

   on Mar 6, 2023

   CollaboratorAuthor

   More actions

   Correction it's not fspec but zarr - the break appears after zarr>2.13.3
4. valeriupredoi commented on Mar 6, 2023

   

   valeriupredoi

   on Mar 6, 2023

   CollaboratorAuthor

   More actions

   OK this is the PR causing this - it seems they have forgotten to update the API - I'll raise an Issue zarr-developers/zarr-python#1304
5. valeriupredoi commented on Mar 6, 2023

   

   valeriupredoi

   on Mar 6, 2023

   CollaboratorAuthor

   More actions

   with 2.13.3 our object is:

   <KVStore: 
   <fsspec.mapping.FSMap object at 0x7ff62cd21630>
    at 0x7ff62cd22140>
   

   with 2.13.6 our object becomes:

   <zarr.storage.FSStore object at 0x7f3120e6d5d0>
   

   so there is a difference in the way the object is treated from one version to another 🤦‍♂️
6. valeriupredoi commented on Mar 6, 2023

   

   valeriupredoi

   on Mar 6, 2023

   CollaboratorAuthor

   More actions

   @davidhassell @bnlawrence I opened this zarr-developers/zarr-python#1362 and right now am gonna pin zarr in our env 👍
7. valeriupredoi commented on Mar 6, 2023

   

   valeriupredoi

   on Mar 6, 2023

   CollaboratorAuthor

   More actions

   we now have a working setup again after #63 but am keeping this open still - am working with the Zarr folks in that issue, and will close ony when we can unpin Zarr and either implement what they recommend, or they fix their bug 👍
8. valeriupredoi

   changed the title [-]Unit tests failing[/-] [+]Unit tests failing (OK for now after pinning Zarr)[/+] on Mar 6, 2023
9. valeriupredoi

   closed this as completedin #65on Mar 7, 2023