perf(lanes): measure work-resolve-issue's idle time to a transient re-fire, 7 days before and after #12804

Abierto
#13,073 5 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
shell

Línea de trabajo

The issue names docs/conventions/pr-pipeline.yaml:1085-1090 for the backoff rules; start there to confirm which transient causes count. Measure the median idle time from transient failure to re-fire over the seven days before and after the 2026-11-03T16:07Z change, then post both measurements here. The after window cannot be complete before 2026-11-10T16:07Z.

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

Descripción

host-run priority: medium status: confirmed work-class: read-only

Refs: #12635

Problem

#12804 (merged 2026-11-03T16:07Z) shortened work-unblock's stranded re-fire backoff to 1 hour for the transient causes (no-run, failed-mint, kill-switch) and kept 3 hours for the rest (docs/conventions/pr-pipeline.yaml:1085-1090). #12635's last done-when item asks for the measured effect; #12635 closed with its other items delivered and this one carried here. It is a measurement over time, which an unattended lane run cannot perform, so it is host work.

Done when

  • On or after 2026-11-10T16:07Z: the median idle time from a transient failure to the re-fire is measured for 7 days before and after, and posted here.

The after window runs from 2026-11-03T16:07Z, so this cannot finish before 2026-11-10T16:07Z.

Filed by Issue Triage. This was generated by AI.

Lenguaje dominante
Shell
Estrellas
22
Forks
2
Merge medio
1 h 18 min
PR fusionados (30 d)
942

Preparar el entorno

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 melodic-software/claude-code-plugins

Todos los issues de melodic-software/claude-code-plugins

Issues similares

Más issues de Shell/Bash

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.