MAINT: Add labels to attack results#1624
Open
behnam-o wants to merge 14 commits intomicrosoft:mainfrom
Open
Conversation
behnam-o
changed the title
rlundeen2
reviewed
Apr 16, 2026
rlundeen2
reviewed
Apr 16, 2026
rlundeen2
approved these changes
Apr 16, 2026
Co-authored-by: hannahwestra25 <[email protected]>
romanlutz
reviewed
Apr 20, 2026
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
4 participants
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.
This PR adds labels to attack results and allows us to remove them from individual message pieces.
Labels are really meaningful in the context of an attack and since all message pieces associated with an attack have the same labels, it makes more sense to store them on the attack result.
this will be followed up with two PRs:
1- Emit a deprecation warning for all public APIs that accept labels that are set on Message Pieces (for example, the message piece constructor itself, or a few upstream functions such as attack_mappers.request_piece_to_pyrit_message_piece , and some rare cases where we do piece.label=<....> after construction
2- [ a couple of releases after above deprecation added], fully remove all label usage on message_piece and only persist in attack result