pythonhuggingface/datasets #7994Not a task: already works

Bump fsspec upper bound constraint

envgap__huggingface__datasets-7994

Original GitHub issue ↗Dated source checkout ↗Opened 2026-02-06

01 / FAILURE SIGNATURE

As reported upstream

No identifying execution failure has been captured.

Not a benchmark task.

The project already builds and runs before the fix, so there is nothing to repair.

02 / ENVIRONMENT RECIPE

Base commit: 025593f2f0722f31fc136e0ae45da4ff44d4416a
Manifest: setup.py
Reproduce: Awaiting issue-specific recipe
Run under trace: Awaiting a meaningful runtime command

03 / ORIGINAL ISSUE TEXT

huggingface/datasets #7994 · read the original issue

Would it be possible to bump fsspec upper bound to the latest (2026.2.0)?

I saw you had some API compat issues in the past (https://github.com/huggingface/datasets/issues/7326) and I understand the need for an upper bound.

But I wonder if you think your CI and tests are a good proxy to catch fsspec API breakage? If that's the case then triggering dataset CI with the latest version of fsspec should tell us whether it's all good right?

Happy to open a PR if needed.

Continue on GitHub ↗

04 / LABELS

Labels from the report text only; not yet run

No supported category has been assigned.

Label rules and the text that matched

[]