Move the worker to the bundle with the 2022–2036 SPM forecast
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
The work is in projects/policyengine-simulation-executor/pyproject.toml (the policyengine[models] pin) and tests/test_spm_runtime_native.py, in test_worker_year_boundary_matches_real_provider. It cannot start until the certifying policyengine.py release (spm-calculator 1.1.0) exists, so first confirm that release is published. Then bump the pin and move the three unavailable-year cases from 2036 to 2037, and run that test file. Done means the test passes and 2037 still returns SPM_YEAR_UNAVAILABLE.
由索引模型根据 Issue 内容生成。
描述
Part of the US 2036 extension, tracked in PolicyEngine/policyengine-api#3926. The worker reads its SPM year boundary from the installed provider, so 2036 becomes available as soon as the worker runs a bundle that certifies spm-calculator 1.1.0 (PolicyEngine/policyengine.py#618). No runtime code changes.
@anth-volk, the steps, once that bundle is released:
- Bundle bump. Move
policyengine[models]inprojects/policyengine-simulation-executor/pyproject.toml(now==6.3.4) to the certifying release. If the policyengine.py release dispatch doesn't cover this repo, a manual pin PR does it. - Tests.
projects/policyengine-simulation-executor/tests/test_spm_runtime_native.pyuses 2036 as the unavailable year intest_worker_year_boundary_matches_real_provider. Those cases become available, so move them to 2037:{"time_period": "2037"};{"start_year": "2037", "window_size": 1};{"start_year": "2036", "window_size": 2}.
- Deploy order. Deploy the worker before or together with policyengine-api's bundle bump and PolicyEngine/policyengine-api#3928. The API checks that the worker's
/versionsmatch. - policyengine-api-v2, if it's still deployed anywhere: it has the same executor layout, so mirror the test change there.
Staging checks:
- A national 2036 economy run completes, and its SPM receipt includes
"2036". budget_window:2027:10completes all ten years.- 2037 still returns
SPM_YEAR_UNAVAILABLE.
🤖 Generated with Claude Code
- 主要语言
- Python
- 星标
- 1
- 派生
- 1
- 平均合并
- 1 天 8 小时
- 30 天内合并 PR
- 51
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
PolicyEngine/policyengine-sim-api 的其他 Issue
-
Update policyengine to 6.7.3可能已有人在做 @policyengine 今天认领。 未关闭
难度 2/5 半天 新手友好度 70/100
PolicyEngine/policyengine-sim-api#823 ·
维护者通常 1 天内回复
-
Integration tests fail due to missing UV virtual environment setup可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭
难度 2/5 1-3 小时 新手友好度 65/100
PolicyEngine/policyengine-sim-api#314 ·
维护者通常 1 天内回复
-
enhancement
难度 4/5 3-5 天 新手友好度 22/100
PolicyEngine/policyengine-sim-api#814 ·
维护者通常 1 天内回复
-
Register weighted-microdata rules: weights aren't values可能已有人在做 @anth-volk 于 3 天前认领。 未关闭
难度 4/5 3-5 天 新手友好度 30/100
PolicyEngine/policyengine-sim-api#806 ·
维护者通常 1 天内回复
-
Refactor within ruff's complexity limits, then select every ruff rule (ALL)可能已有人在做 @anth-volk 于 3 天前认领。 未关闭
难度 4/5 3-5 天 新手友好度 15/100
PolicyEngine/policyengine-sim-api#803 ·
维护者通常 1 天内回复
查看 PolicyEngine/policyengine-sim-api 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 88/100
NousResearch/hermes-agent#140958 ·
维护者通常 1 天内回复
-
bisect
难度 2/5 1-3 小时 新手友好度 72/100
dtcxzyw/llvm-bisect-service#548 ·
-
难度 2/5 1-3 小时 新手友好度 82/100
sallowayma-git/IELTS-practice#248 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 65/100
anthropics/claude-plugins-official#6763 · 10 条评论 · 10 个 reaction ·
维护者通常 3 天内回复
-
难度 2/5 1-3 小时 新手友好度 85/100
维护者通常 1 天内回复