fix(rejudge): preserve the pre-re-judge record outside the published tree - #22
Merged
Merged
Conversation
…tree Writing the backup beside results.json left a fourth file in each run directory, so a consumer syncing the corpus also shipped superseded scores. It now lands in a sibling tree mirroring the corpus layout, overridable with --backup-root.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Writing the backup beside
results.jsonleft a fourth file in each run directory, so anything syncing the corpus also shipped superseded scores next to the corrected ones.The pre-re-judge record now lands in a sibling tree mirroring the corpus layout —
<backup-root>/<combo>/<task>/<run_id>/results.json— so a path in either tree names the same run, the published tree keeps exactly its three artifacts, and the correction stays auditable.--backup-rootoverrides the location.Verified the default resolves to the sibling prefix for a corpus-shaped run path, and that a custom root is honoured. Ruff clean.