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

Segmented US national runs wait on stuck regional children until the parent times out

Abierto
  • ¿Algo no está bien?
#794 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.

  • #795 de @anth-volk — abierto

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
25/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
python
Área
backend, distributed-systems

Línea de trabajo

Start with the parent run_simulation function, which waits on regional child runs with no per-child deadline and is killed by the 3,600 s Modal timeout. The payload does not name the files or tests involved, so locate the orchestration code yourself. Done means a stuck child is cancelled and retried once, the run fails with the region group named, and the parent cancels its children before its own timeout. PR #795 already targets this issue, so check it before starting.

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

Descripción

Problem

A segmented US national run waits on each regional child with no deadline of its own. If a child never finishes, the parent run_simulation waits until its 3,600 s Modal timeout kills it. Because the parent is killed rather than failing in code, nothing cancels its children, and they keep running.

On 9 October 2026, both US national reports for 2023 hit this. They used the same policy and started at about 05:45 UTC.

  • Their 20 regional children were re-run 180 and 131 times on new containers, and none finished. The few that logged an error were interrupted during dataset loading after 229–517 s.
  • First report: the parent ended at 3,599.8 s with Modal's InputCancellation ("Input was cancelled by user"), which is its timeout. Its children kept restarting for about another 50 minutes.
  • Second report: the parent failed after 3,167 s with Server has lost track of input, from polling a restarting child.

Reports for other years needed at most three extra child runs, and all succeeded.

Expected

  • A child with no result within a reasonable deadline is cancelled and retried once.
  • The run fails with a clear message naming the region group if the retry also fails or runs out of time.
  • The parent fails in code, and cancels its children, before its Modal timeout.

Follow-up (not in scope)

Find why the 2023 children's containers kept being terminated, which needs Modal container logs. Respawned children also start new traces with no parent span.

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.