Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

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

Aperta
  • Qualcosa non va?
#794 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@anth-volk ci sta già lavorando.

Dal 13/10/2026.

  • #795 di @anth-volk — aperta

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
25/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
python
Ambito
backend, distributed-systems

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
Python
Stelle
1
Fork
1
Merge medio
1g 4h
PR unite (30g)
27

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di PolicyEngine/policyengine-sim-api

Tutte le issue di PolicyEngine/policyengine-sim-api

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.