Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

[BLOCKED] FEAT: Drill into paired Scenario outcome conversations

Abierto
  • ¿Algo no está bien?
#3,389 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

@shashank03-dev ya está trabajando en esto.

Desde el 20/10/2026.

  • #3390 de @shashank03-dev — cerrado sin fusionar
  • #3391 de @shashank03-dev — abierto

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
10/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Estancado
Stack tecnológico
python
Área
ai, frontend

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Python
Estrellas
4.6k
Forks
962
Merge medio
2 d 15 h
PR fusionados (30 d)
398

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

  • Sin Dockerfile ni archivo de Docker Compose
  • Tiene una plantilla de pull request
  • Sin guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de microsoft/PyRIT

Todos los issues de microsoft/PyRIT

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.