The dataset viewer is not available for this subset.
Exception: SplitsNotFoundError
Message: The split names could not be parsed from the dataset config.
Traceback: Traceback (most recent call last):
File "/usr/local/lib/python3.14/site-packages/datasets/inspect.py", line 286, in get_dataset_config_info
for split_generator in builder._split_generators(
~~~~~~~~~~~~~~~~~~~~~~~~~^
StreamingDownloadManager(base_path=builder.base_path, download_config=download_config)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File "/usr/local/lib/python3.14/site-packages/datasets/packaged_modules/webdataset/webdataset.py", line 81, in _split_generators
first_examples = list(islice(pipeline, self.NUM_EXAMPLES_FOR_FEATURES_INFERENCE))
File "/usr/local/lib/python3.14/site-packages/datasets/packaged_modules/webdataset/webdataset.py", line 32, in _get_pipeline_from_tar
fs: fsspec.AbstractFileSystem = fsspec.filesystem("memory")
~~~~~~~~~~~~~~~~~^^^^^^^^^^
File "/usr/local/lib/python3.14/site-packages/fsspec/registry.py", line 302, in filesystem
cls = get_filesystem_class(protocol)
File "/usr/local/lib/python3.14/site-packages/fsspec/registry.py", line 239, in get_filesystem_class
raise ValueError(f"Protocol not known: {protocol}")
ValueError: Protocol not known: memory
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/src/services/worker/src/worker/job_runners/config/split_names.py", line 71, in compute_split_names_from_streaming_response
for split in get_dataset_split_names(
~~~~~~~~~~~~~~~~~~~~~~~^
path=dataset,
^^^^^^^^^^^^^
config_name=config,
^^^^^^^^^^^^^^^^^^^
token=hf_token,
^^^^^^^^^^^^^^^
)
^
File "/usr/local/lib/python3.14/site-packages/datasets/inspect.py", line 340, in get_dataset_split_names
info = get_dataset_config_info(
path,
...<6 lines>...
**config_kwargs,
)
File "/usr/local/lib/python3.14/site-packages/datasets/inspect.py", line 291, in get_dataset_config_info
raise SplitsNotFoundError("The split names could not be parsed from the dataset config.") from err
datasets.inspect.SplitsNotFoundError: The split names could not be parsed from the dataset config.Need help to make the dataset viewer work? Make sure to review how to configure the dataset viewer, and open a discussion for direct support.
Next.js Selfbench
Next.js Selfbench is a 47-task software-engineering evaluation packaged for the Harbor evaluation framework. Each task asks an agent to implement a change in a frozen revision of vercel/next.js, then evaluates the resulting patch with task-specific tests.
This repository contains the raw evaluation only. It does not include model outputs, scores, costs, or benchmark result artifacts.
Use
Download the raw task package with the Hugging Face CLI:
hf download dari-ai/nextjs-selfbench --repo-type dataset --local-dir nextjs-selfbench
The downloaded directory is a Harbor task collection. Configure your Harbor job to use either the collection or an individual top-level task directory, such as nextjs-selfbench/nextjs-pr-96284. Agent credentials and agent configuration are intentionally not included in this dataset. See the Harbor documentation for installation and job configuration.
Contents
Each top-level task directory contains:
task.toml: Harbor task configuration and source metadata.instruction.md: the request shown to the coding agent.environment/: the frozen Next.js repository and build environment.tests/: verifier setup and task-specific tests.solution/: the reference patch and solution script..selfbench-manifest.json: task provenance and integrity checksums.
tasks.tsv provides a compact manifest of all 47 task IDs, difficulty labels, and definition/test/solution checksums.
Reproducibility
Each task pins a Next.js base commit and includes its repository archive, so it does not depend on future upstream changes. The task definitions use Harbor schema version 1.4 and were generated with Selfbench compiler revision 22; these are provenance fields, not additional installation requirements.
Important evaluation note
The repository includes verifier tests and reference solutions because this is the complete raw evaluation package. Do not expose tests/ or solution/ to an agent. Harbor runs the verifier in its separate verifier environment when the task is run normally; preserve that separation if adapting these tasks to another framework.
Licensing
The embedded Next.js source is distributed under its upstream license. Other files retain the terms of their respective sources. Review the included upstream license and source metadata before redistributing modified versions.
- Downloads last month
- 2