Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

FEAT: Drill into paired Scenario outcome conversations

Offen
  • Stimmt etwas nicht?
#3,389 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 2 Tagen

@shashank03-dev arbeitet bereits daran.

Seit 20.10.2026.

  • #3390 von @shashank03-dev — ohne Merge geschlossen
  • #3391 von @shashank03-dev — offen

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
10/100
Issue-Typ
Feature
Klarheit
Klar beschrieben
Aktivitätsstatus
Veraltet
Tech-Stack
python
Bereich
ai, frontend

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.

Vorherrschende Sprache
Python
Sterne
4.7k
Forks
980
Ø Merge
2 T. 7 Std.
Gemergte PRs (30 T.)
446

Entwicklungsumgebung

In Codespaces öffnen

Startet den Dev-Container des Projekts im Browser, mit Ihrem eigenen GitHub-Konto.

  • Kein Dockerfile und keine Docker-Compose-Datei
  • Hat eine Pull-Request-Vorlage
  • Kein Beitragsleitfaden

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus microsoft/PyRIT

Alle Issues in microsoft/PyRIT

Ähnliche Issues

Weitere Issues zu Python

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.