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

Stage 12 coordinator can outlive its timeout while waiting and leaves workers running

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

Los mantenedores suelen responder en 1 día

@anth-volk ya está trabajando en esto.

Desde el 13/10/2026.

  • #793 de @anth-volk — abierto

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
20/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
python
Área
backend

Línea de trabajo

The issue does not name the coordinator's source file, so start by finding where the Stage 12 coordinator waits on the baseline and reform workers, using the 3,000 s wait and 4,500 s Modal timeout as search terms. Check the existing pull request #793 before starting, since it already targets this work. Done means both waits share one deadline that leaves time to save the outcome, and a failed or timed-out worker cancels the unfinished sibling and records it as failed.

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

Descripción

Problem

The Stage 12 coordinator can be killed before it records a failure, and it leaves workers running after a comparison has failed.

  • Separate wait timeouts: the coordinator waits up to 3,000 s for the baseline worker, then up to a fresh 3,000 s for the reform worker. Its own Modal timeout is 4,500 s. When workers are queued, the two waits can exceed that, and Modal kills the coordinator before it saves the failure.
  • Siblings keep running: when one worker's wait fails or times out, the other worker keeps running. That can mean a 32 GB container for up to 50 minutes on a comparison that has already failed.

One production report from 6 to 13 October 2026 waited 3,000.0175 s for baseline and then stored TimeoutError. Its reform worker had already been interrupted after about 305 s.

Expected

  • Both waits share one deadline that leaves the coordinator time to save the outcome before its Modal timeout.
  • When one worker fails or times out, the coordinator cancels every unfinished worker and records the cancelled one as failed.

Observing baseline and reform concurrently is out of scope here; it is part of #712.

Lenguaje dominante
Python
Estrellas
1
Forks
1
Merge medio
1 d 4 h
PR fusionados (30 d)
27

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 PolicyEngine/policyengine-sim-api

Todos los issues de PolicyEngine/policyengine-sim-api

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.