MAINT: Leakage Scenario Refactor and Scenario Improvements#1687
Merged
rlundeen2 merged 11 commits intomicrosoft:mainfrom May 6, 2026
Merged
MAINT: Leakage Scenario Refactor and Scenario Improvements#1687rlundeen2 merged 11 commits intomicrosoft:mainfrom
rlundeen2 merged 11 commits intomicrosoft:mainfrom
Conversation
jsong468
reviewed
May 5, 2026
jsong468
reviewed
May 5, 2026
rlundeen2
changed the title
jsong468
reviewed
May 5, 2026
jsong468
reviewed
May 5, 2026
jsong468
reviewed
May 5, 2026
jsong468
reviewed
May 5, 2026
jsong468
reviewed
May 5, 2026
…5_04_leakage_update
- frontend_core: supported_parameters is now a 3-tuple (name, desc, default) - scenario: _validate_stored_scenario now raises ValueError instead of returning bool - scenario: not-found case now raises instead of silently creating new result Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
jsong468
approved these changes
May 6, 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
2 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.
get_chat_targetmethod to scorers for easier reuse between scenarios; making this easier to use because both it and cyber will now respect default scorers and not require the specific "UNSAFE" endpointaccepts_scorer_override booleanwith aScorerOverridePolicyenum (SKIP/WARN/RAISE) that introspects the attack's type annotation at runtime, so incompatible scorer overrides are handled gracefully instead of requiring manual opt-out flags (important to use TAP when a scenario defines a specific scorer)