Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

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

クローズ
  • 何か問題がありますか？
#794 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

@anth-volk がすでに取り組んでいます。

2026年10月13日 から。

  • #795 @anth-volk による — オープン

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
25/100
issue の種類
バグ
明瞭さ
おおむね明確
活発さ
活発
技術スタック
python
領域
backend, distributed-systems

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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.

主要言語
Python
スター
1
フォーク
1
平均マージ
1日 11時間
マージ済み PR（30日）
50

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

PolicyEngine/policyengine-sim-api のほかの issue

PolicyEngine/policyengine-sim-api の issue をすべて見る

似ている issue

Python の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。