feat: verify any published version and default to the as-published history - #50
Merged
Conversation
…story Add --version to reproduce and verify_published_record.py in both modes. The output names the version and methodology_id verified, and rows before a version's effective time are labelled back-calculated. When latest.json advertises a per-SKU history path, the default verifies the as-published history: the value live at each observation, across methodology versions. Only that SKU's succession methodology ids are accepted there; versioned keyspaces keep strict single-version identity. Without the field, the default follows current_version and prints a notice. Document the corpus keyspaces and exit codes in the README, keep the launch transcript as a version 5 record, and add the change-log entry. Tests cover mixed-methodology days, version routing, pointer snapshots, invalid paths and identities, digest failure, fallback, and effective-time boundaries. Signed-off-by: hobbyistz <293619914+hobbyistz@users.noreply.github.com>
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.
Add --version to reproduce and verify_published_record.py in both modes.
The output names the version and methodology_id verified, and rows before a
version's effective time are labelled back-calculated.
When latest.json advertises a per-SKU history path, the default verifies the
as-published history: the value live at each observation, across methodology
versions. Only that SKU's succession methodology ids are accepted there;
versioned keyspaces keep strict single-version identity. Without the field,
the default follows current_version and prints a notice.
Document the corpus keyspaces and exit codes in the README, keep the launch
transcript as a version 5 record, and add the change-log entry.
Tests cover mixed-methodology days, version routing, pointer snapshots,
invalid paths and identities, digest failure, fallback, and effective-time
boundaries.
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.