Unit tests failing (OK for now after pinning Zarr)

[valeriupredoi]

Our tests are currently failing, see fails - it's very possible new versions of fsspec have changed their API, I will check this now (cheers @davidhassell for alerting me 🍺 )

[valeriupredoi]

Correction it's not fspec but zarr - the break appears after zarr>2.13.3

[valeriupredoi]

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

[valeriupredoi]

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 🤦‍♂️

[valeriupredoi]

@davidhassell @bnlawrence I opened this zarr-developers/zarr-python#1362 and right now am gonna pin zarr in our env 👍

[valeriupredoi]

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 👍