Skip to content

MAINT: Add atomic attack context to scenario errors - #3277

Merged
Roman Lutz (romanlutz) merged 1 commit into
microsoft:mainfrom
huong8373tt-beep:fix/p311-08-atomic-attack-exception-context
Oct 17, 2026
Merged

Roman Lutz (romanlutz) merged 1 commit into
microsoft:mainfrom
huong8373tt-beep:fix/p311-08-atomic-attack-exception-context

Conversation

@huong8373tt-beep

Copy link
Copy Markdown
Contributor

Description

Implements the remaining Scenario investigation for P311-08 from #3166.

When an atomic attack fails during parallel scenario execution, the original exception now receives a safe note naming the atomic attack and scenario before it is aggregated or re-raised. This preserves the original exception identity, type, traceback, cancellation behavior, and existing single-error/ExceptionGroup contract. The note does not include seed or prompt content.

Tests and Documentation

  • python -m pytest tests/unit/scenario/core/test_scenario.py -q — 111 passed.
  • pre-commit run --files pyrit/scenario/core/scenario.py tests/unit/scenario/core/test_scenario.py — passed, including Ruff and type checks.
  • No documentation changes were needed.

Slai Agent Runtime assisted with investigation, implementation, and tests. The account owner reviewed and authorized this contribution.

@romanlutz
Roman Lutz (romanlutz) added this pull request to the merge queue Oct 17, 2026
Merged via the queue into microsoft:main with commit 0b6b28e Oct 17, 2026
103 of 106 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants