Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

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

Fechada
  • Algo errado?
#794 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

@anth-volk já está trabalhando nisso.

Desde 13/10/2026.

  • #795 de @anth-volk — aberto

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
25/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
python
Domínio
backend, distributed-systems

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.

Linguagem predominante
Python
Estrelas
1
Forks
1
Merge médio
1d 11h
PRs com merge (30d)
50

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de PolicyEngine/policyengine-sim-api

Todas as issues de PolicyEngine/policyengine-sim-api

Issues semelhantes

Mais issues de Python

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.