-
Notifications
You must be signed in to change notification settings - Fork 823
FIX: pyrit_shell run fails for every scenario with a flag-collision error
#2303
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
jsong468
wants to merge
1
commit into
microsoft:main
Choose a base branch
from
jsong468:pyrit_shell_flag_collision_bug
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+76
−11
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Rich agrees with this comment but it is copilot generated:
The docstring says this drop mirrors
pyrit_scan._add_scenario_params_from_api, but it only mirrors the built-in collision case._add_scenario_params_from_apiuses a singleseen_flagsset and silently drops any duplicate flag (first-wins), including scenario-vs-scenario. Here we instead raise on a scenario-vs-scenario collision. Net effect: a scenario definition that runs fine underpyrit_scanwould hard-fail underpyrit_shell— the two entrypoints aren't actually at parity for that case.In practice the raise branch is close to dead code (param names are Python identifiers and the
_→-normalization is injective over identifiers, so two distinct names can't collide), so severity is low. But it's worth either aligning withpyrit_scan(silently drop, first-wins) for true parity, or softening the "mirroring" wording to call out the intentional divergence and why.