Skip to content

Reference fsspec store has mismatching asynchron-ity #2946

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Tracked by #36
juntyr opened this issue Apr 3, 2025 · 0 comments
Open
Tracked by #36

Reference fsspec store has mismatching asynchron-ity #2946

juntyr opened this issue Apr 3, 2025 · 0 comments
Labels
bug Potential issues with the zarr-python library

Comments

@juntyr
Copy link

juntyr commented Apr 3, 2025

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

import xarray as xr
import gribscan

ds = xr.open_dataset(
    f"reference::https://a3s.fi/compression.lab.climet.eu/hplp_ml_reduced_gg_all_params_levels_1-15_all_steps.grib.ref",
    engine="zarr", consolidated=False,
)
ds

Additional output

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Potential issues with the zarr-python library
Projects
None yet
Development

No branches or pull requests

1 participant