test(candidate-execution): use protected trace writes in fixtures - #1106
Merged
Conversation
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.
Candidate execution fixtures wrote raw trace IDs directly to storage.
When an ID matched a redaction rule, finalization could not find the protected record.
This caused the single failure in main CI.
Use the supplied trace store for all 19 affected fixture writes.
Force a sensitive-looking ID in the receipt test and inspect the stored identity when checking redaction.
Production code and credential protection are unchanged.
Validation:
e28a6b64c0a3f09ee6463f4f5e4e79d6938cc56chas the exact reviewed tree.