Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

[BLOCKED] FEAT: Drill into paired Scenario outcome conversations

オープン
  • 何か問題がありますか？
#3,389 コメント 2 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 2 日以内に返信

@shashank03-dev がすでに取り組んでいます。

2026年10月20日 から。

  • #3390 @shashank03-dev による — マージされずにクローズ
  • #3391 @shashank03-dev による — オープン

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
10/100
issue の種類
機能追加
明瞭さ
明確に書かれている
活発さ
停滞
技術スタック
python
領域
ai, frontend

調査の方向性

The issue places this work on the Scenario run results page and says to reuse backend pairing semantics and existing conversation routes. First inspect the implementation from PR #3337 and the open follow-up PR #3391, then check whether the stated ownership block has been cleared. Done means transition rows can load and collapse matching pairs on demand, with bounded loading, accessible navigation, and clear loading, empty, and retryable error states.

索引モデルが issue の本文から書いたものです。

説明

feature-request help wanted
Is your feature request related to a problem? Please describe.

The Paired outcomes panel on a Scenario run reports transitions such as one baseline failure becoming an attack success, but there is no way to inspect which objective and conversations produced that transition. Aggregate counts alone make it difficult to investigate the differences.

Describe the solution you'd like

BLOCKED pending @shashank03-dev's decision. He may want to pick this up as the author of #3337. Please do not start implementation or claim the work until he decides whether he wants to take it. If he opts in, coordinate ownership with him; if he declines, this can be opened to other contributors. The help wanted label does not override this block.

On the Scenario run results page:

  • Make each paired-outcome transition row expandable on demand and collapsible again.
  • Expanding a row should load the matching baseline/attack pairs, rather than eagerly loading all conversations with the initial comparison.
  • Show the objective or logical seed and useful context for both sides of each pair, including their outcomes. Provide clear navigation to the relevant baseline and attack conversations using the existing conversation routes and Scenario context.
  • Keep the selected groups, latest top-level attempt rules, and decided-pair population consistent with the displayed transition count. Reuse backend pairing semantics rather than calculating a separate cohort in the GUI.
  • Support bounded loading or pagination for large categories, keyboard-accessible expansion/navigation, and clear loading, empty, and retryable error states. Users must be able to collapse an expanded category again.

For example, expanding Failure -> Success: 1 should reveal the matching pair and let the user inspect the baseline conversation and the successful attack conversation.

Describe alternatives you've considered, if relevant

Keeping aggregate counts only requires users to locate matching results manually. A single conversation link on a category would not work when it contains multiple pairs. Loading every conversation with the initial comparison would add unnecessary work for large Scenario runs. On-demand row expansion lets users investigate the transition they care about without that upfront cost.

Additional context

Follow-up to merged PR #3337. This belongs to Scenario run results, not general attack-result analytics: the saved run plan identifies the baseline, attack groups, and matched seed population.

This issue is coordination-blocked pending @shashank03-dev deciding either way; no follow-up implementation should start until that block is cleared.

主要言語
Python
スター
4.6k
フォーク
962
平均マージ
2日 13時間
マージ済み PR（30日）
417

環境構築

Codespaces で開く

このプロジェクトの開発コンテナを、あなたの GitHub アカウントでブラウザ上に起動します。

  • Dockerfile・Docker Compose ファイルなし
  • プルリクエストのテンプレートあり
  • コントリビューションガイドなし

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

microsoft/PyRIT のほかの issue

microsoft/PyRIT の issue をすべて見る

似ている issue

Python の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。