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 80, in _split_generators
raise ValueError(
...<2 lines>...
)
ValueError: The TAR archives of the dataset should be in WebDataset format, but the files in the archive don't share the same prefix or the same types.
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 68, 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.
SWE-Kernel recovery snapshots
Public recovery copy for the SWE-Kernel project before server reclamation. Code backup: https://github.com/huangd1999/SWE-Kernel. The original workspace is also included in the recovery snapshot.
Upload status
Backup is in progress. The owner explicitly authorized making the complete original backup public after being informed it includes gold patches, hidden evaluator code, unreleased tasks and curation records. The earlier private-storage quota block is resolved by that visibility choice; the remaining uploads have resumed.
GitHub code backup is verified at commit cfe98f29d5c3cb4f50585f22fa0f6ddc9f0dc9c4 (4,212 files). The original workspace archive has been uploaded, downloaded again and SHA-256 verified. The complete local data baseline consists of 33 ordered chunks, totaling 138,609,232,987 bytes, and passed all SHA-256, zstd-stream and tar-list checks. Incremental-001 adds the final source checkpoint and infrastructure-invalid FLA1033 record; FLA1177 remained running at its capture time. Environment preservation is being prepared separately.
A remote backup is complete only when every manifest-listed part is present and verified. Do not treat partial archives as recoverable. A final BACKUP_COMPLETE.json will be published after required uploads and checks finish.
Benchmark status at the start of backup
The central ledger records 90 C4 replayed task drafts (67 Repair, 23 Optimize), with 0 C6 accepted Full tasks. The target remains 2,294 accepted tasks. Additional sealed worker results may await ledger ingestion. Source-readiness v004 records 2,118 complete and 176 pending candidates; C3 readiness v5 records 7 ready. The 47-packet independent second review collected 309 rows: 239 agreed routes and 70 unresolved disputes. These counts are separate stages, not counts to add together.
Recovery layout
- Restore the code checkout to
/home/nvidia/SWE-Kernel. - Restore project data to
/data/swe-kernel; Git alternates and artifact paths depend on this location. - Recreate workspace symlinks
runs -> /data/swe-kernel/runsandcaches -> /data/swe-kernel/caches. - Verify each archive part against its SHA-256 manifest before concatenating/decompressing.
- Apply baseline and any incremental data archives in the documented order to an empty recovery destination. Incremental archives can contain deletion records.
- Review the Docker inventory and restore pinned images before replay. Do not silently rewrite environment locks to accommodate missing image digests.
- Task code, builds, reproducers and GPU evaluation must run only in the restricted Docker protocol recorded by AGENTS.md.
The archive retains source-repository license files and curation evidence. It is not a public dataset release or an assertion that C5/C6 acceptance is complete. Authentication caches, personal SSH keys and the backup staging directory are excluded.
- Downloads last month
- 49