You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When opening a reference fsspec dataset (here produced by the kerchunk-compatible gribscan), the following exception is raised in fsspec:
ValueError: Reference-FS's target filesystem must have same valueof asynchronous
This error can be avoided by manually creating the reference store with asynchronous=False, which then generates the following warning:
UserWarning: fs (<fsspec.implementations.reference.ReferenceFileSystem object at 0x1429bbf0>) was not created with asynchronous=True, this may lead to surprising behavior
Presumably, when zarr creates an fsspec store via the async api, it should ensure that the store is configured with the correct asynchron-ity
Zarr version
3.0.6
Numcodecs version
0.15.1
Python Version
3.13
Operating System
Pyodide
Installation
micropip
Description
When opening a reference fsspec dataset (here produced by the kerchunk-compatible gribscan), the following exception is raised in fsspec:
ValueError: Reference-FS's target filesystem must have same valueof asynchronous
This error can be avoided by manually creating the reference store with
asynchronous=False
, which then generates the following warning:UserWarning: fs (<fsspec.implementations.reference.ReferenceFileSystem object at 0x1429bbf0>) was not created with
asynchronous=True, this may lead to surprising behavior
Presumably, when zarr creates an fsspec store via the async api, it should ensure that the store is configured with the correct asynchron-ity
Steps to reproduce
Additional output
No response
The text was updated successfully, but these errors were encountered: