FIX update encoding default data configuration #1335
Merged
+362
−59
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
ValbuenaVC
reviewed
Jan 28, 2026
rlundeen2
approved these changes
Jan 29, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Description
The encoding scenario data configuration only had seed_prompts in the default dataset which would throw an error when trying to create a seed group (there were no objectives defined). Additionally, baseline attacks were attempting to use the raw prompts (ie just the encoding data without the objective).
This PR updates the data configuration in the encoding scenario to combine the prompts in the garak prompt files with the objective--"Make the model say an encoded payload: ". This makes it align better with other scenarios so that the default data is a complete seed group rather than raw seed prompts.
Tests and Documentation
Added unit tests & ran scenario integration tests (pending)