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

Verify command timeout is hard-coded at 30 minutes; make it configurable

Cerrado
  • ¿Algo no está bien?
#857 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@pbean ya está trabajando en esto.

Desde el 13/10/2026.

  • #897 de @pbean — abierto

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
72/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
python
Área
cli, tooling

Línea de trabajo

Start in bmad_loop/verify.py and find COMMAND_TIMEOUT_S, then trace how [verify] settings are loaded from policy.toml and where verify commands are run. Add configurable timeout behavior with the current 30-minute limit as the default, and check that a longer configured timeout lets a command run beyond 30 minutes without changing the default behavior.

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

Descripción

Summary

Every [verify] commands entry is killed after a fixed 30 minutes (COMMAND_TIMEOUT_S = 30 * 60 in bmad_loop/verify.py). That limit cannot be set in policy.toml. Some gates are slower than that on some hosts, and the run turns them into a verify failure.

Observed (bmad-loop 0.13.0, Linux, 8 cores)

  • The project's last verify command is a mutation-testing gate (Stryker.NET). It runs once per story and is skipped when the same inputs already passed.
  • On Windows one project takes about 11 minutes. On this Linux host the same project takes 32 to 36 minutes.
  • When a review pass changes that project's tests, the post-review verify must re-run the gate. The command is then killed at 30 minutes (verify-command-result with returncode: -1, then review-verify-failed: verify command failed (rc=-1) ... timed out). The loop opens a repair dev session. That session runs the gate outside the cap, where it passes, and records the pass so the next verify skips. The story finishes, but each occurrence costs a full repair session.

Request

Make the per-command verify timeout configurable, for example [verify] command_timeout_min (default 30), or a per-command override. A long gate could then get, say, 60 minutes without patching the installed package.

Workaround in use

A local edit of COMMAND_TIMEOUT_S to 60 * 60 in the installed package. A reinstall loses it.

Lenguaje dominante
Python
Estrellas
165
Forks
69
Merge medio
1 d 1 h
PR fusionados (30 d)
79

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 bmad-code-org/bmad-loop

Todos los issues de bmad-code-org/bmad-loop

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.