Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

[BLOCKED] FEAT: Drill into paired Scenario outcome conversations

Aperta
  • Qualcosa non va?
#3,389 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 2 giorni

@shashank03-dev ci sta già lavorando.

Dal 20/10/2026.

  • #3390 di @shashank03-dev — chiusa senza merge
  • #3391 di @shashank03-dev — aperta

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
10/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Ferma
Stack tecnologico
python
Ambito
ai, frontend

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
Python
Stelle
4.7k
Fork
980
Merge medio
2g 13h
PR unite (30g)
407

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

  • Nessun Dockerfile né file Docker Compose
  • Ha un modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di microsoft/PyRIT

Tutte le issue di microsoft/PyRIT

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.