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

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

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

I maintainer di solito rispondono entro 1 giorno

@anth-volk ci sta già lavorando.

Dal 30/9/2026.

  • #712 di @anth-volk — aperta
  • #793 di @anth-volk — chiusa senza merge

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
20/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Ferma
Stack tecnologico
python
Ambito
backend

Direzione di ricerca

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.

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

Descrizione

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.

Lingua principale
Python
Stelle
1
Fork
1
Merge medio
1g 7h
PR unite (30g)
40

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.