Skip to content

SCROLLS tasks fail to load with recent datasets (dataset scripts no longer supported) #3859

Description

@bongho

The scrolls_* tasks fail at data loading on recent datasets. tau/scrolls is a script-based dataset, and datasets has removed support for dataset scripts (and trust_remote_code), so the load now raises.

Env: datasets==5.0.0, lm_eval==0.4.13.dev0

from datasets import load_dataset
load_dataset("tau/scrolls", "qasper", split="validation")
# RuntimeError: Dataset scripts are no longer supported, but found scrolls.py

Same failure via lm_eval --tasks scrolls_qasper. It affects all seven scrolls tasks (scrolls_govreport, scrolls_qasper, scrolls_narrativeqa, scrolls_qmsum, scrolls_quality, scrolls_summscreenfd, scrolls_contractnli).

lm_eval/tasks/scrolls/task.py sets DATASET_PATH = "tau/scrolls", and _download_metric() pulls metrics/scrolls.py from the same repo — both rely on the loading script that datasets no longer runs. pyproject.toml has datasets>=2.16.0 with no upper bound, so a fresh install hits this.

Two ways forward:

  • Pin datasets (e.g. <4) as a stopgap, though that holds back tasks needing newer datasets.
  • Migrate scrolls to a parquet dataset on the Hub. There's no clean labeled mirror right now, so this means converting the gold-bearing splits and re-implementing the metric (also script-based). Same root cause as Add ZeroScrolls Benchmark #1083.

Happy to help with the migration if that's the preferred route.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions