XY-913: Reuse operator snapshots for status - #322
Merged
Conversation
…status","authority":"XY-913"}
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
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.
Summary
decodex statusreuse the local operator listener snapshot when it is fresh and covers the requested projectstatus_cached_snapshot_unavailabledetails when cache reuse is unsafeValidation
cargo test -p decodex status_cache --all-features -- --test-threads=1cargo test -p decodex status_snapshot --all-features -- --test-threads=1cargo clippy --all-features --all-targets -p decodex -- -D warningscargo make testpython3 /Users/x/.codex/plugins/cache/hack-ink/playbook/0.3.0/scripts/semantic_drift_audit.py --rev HEADwith agent verdict: passcargo make checkstatus_cached_snapshot_unavailableinstead of trusting an incompatible cached snapshot