Repository navigation
FIX: keep memory labels on the SequentialAttack result - #3111
Merged
Richard Lundeen (richlundeen) merged 6 commits intoOct 12, 2026
Merged
Richard Lundeen (richlundeen) merged 6 commits into
Richard Lundeen (richlundeen) merged 6 commits into
Conversation
Richard Lundeen (richlundeen)
approved these changes
Oct 11, 2026
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Oct 11, 2026
Contributor
Author
|
The one red job is an analytics timeout in |
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.
Fixes #3110.
Passes
labels=context.memory_labelstoSequentialAttackResult, like the other attacks and the error path do. Test checks the completed result carries the context labels, and it fails on main. tests/unit/executor plus the adaptive scenario tests: 1562 passed.