Skip to content

Dataset self-verification fails on fresh downloads: checksums.sha256 stale for README.md (solve + reference) #28

Description

@wayfind

Summary

Both FrontierChallenge HF datasets currently fail their own tools/verify_*.py on a fresh main download, which aborts setup.sh for every new evaluator.

Details

  • apodex/FrontierChallenge (solve): README.md at main hashes to e99e2400…, but checksums.sha256 still records 81a5032a… (the README as of revision 79818fdd, before the two citation edits 0cad1a9e and 93e1cc68). tools/verify_dataset.pychecksum failures: README.md.
  • apodex/FrontierChallenge-reference (gated): same pattern — README was edited without regenerating its checksums.sha256 entry, so tools/verify_reference_dataset.py fails the same way. (All 97 verifier archives still pass their manifest/registry commitments — only the doc line is stale.)

Impact

scripts/setup.sh hard-fails at verify_dataset_tools, so a by-the-book install cannot complete without manually pinning README to 79818fdd (solve) / regenerating the checksum line (reference).

Suggested fix

Regenerate checksums.sha256 whenever docs change — a tiny CI check on the dataset repos would prevent recurrence.

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