Upgrade simulation workers to PolicyEngine 6.2.3 for UK region filtering
维护者通常 1 天内回复
已经有一个关联 PR 被合并了。
- #733 来自 @anth-volk —— 已合并
评估
调研方向
The change is a policyengine pin in both dependency locations: the simulation executor's lockfile and the Modal image group. Check that the published release exists before editing, since PyPI currently returns 404 for 6.2.3. Done means the pin is updated, uv lock --upgrade-package policyengine regenerates the lockfile, and the executor tests pass. Linked PR #733 already implements this, so coordinate there rather than starting a parallel change.
由索引模型根据 Issue 内容生成。
描述
Require the corrected UK country filtering from PolicyEngine/policyengine.py#565 (tracking issue PolicyEngine/policyengine.py#564) in the simulation executor and its Modal image. The expected next patch release is policyengine==6.2.3; PyPI currently publishes 6.2.2 and returns HTTP 404 for 6.2.3.
Pin policyengine[models]==6.2.3 in both dependency locations. Scotland, Wales, and Northern Ireland must select the stored household region values SCOTLAND, WALES, and NORTHERN_IRELAND. England selects the nine English regions. The worker must not require a raw household country column.
Open the dependency PR now. Dependency-resolution failure because 6.2.3 does not yet exist is expected. Keep the actual existing lockfile until the package is published; do not invent release artifact URLs or hashes, use a Git checkout as a substitute, or weaken the version pin.
Before merge: confirm the published release contains the upstream fix, regenerate the executor lockfile with uv lock --upgrade-package policyengine, run its tests and image checks, and verify the same requirement applies to the Modal image group. If another release takes 6.2.3 first, update the proposed pin to the actual fixed release.
Implementation PR: #733. After merge: deploy and qualify the corrected simulation worker and confirm the gateway advertises the fixed bundle before API v1 restores the Scotland population test in PolicyEngine/policyengine-api#3877 (issue PolicyEngine/policyengine-api#3876). Temporary test removal: PolicyEngine/policyengine-api#3875 (issue PolicyEngine/policyengine-api#3874).
- 主要语言
- Python
- 星标
- 1
- 派生
- 1
- 平均合并
- 1 天 6 小时
- 30 天内合并 PR
- 24
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
PolicyEngine/policyengine-sim-api 的其他 Issue
-
Integration tests fail due to missing UV virtual environment setup可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭
难度 2/5 1-3 小时 新手友好度 65/100
PolicyEngine/policyengine-sim-api#314 ·
维护者通常 1 天内回复
-
Update policyengine to 6.2.7可能已有人在做 @policyengine 今天认领。 未关闭
难度 1/5 1 小时以内 新手友好度 55/100
PolicyEngine/policyengine-sim-api#745 ·
维护者通常 1 天内回复
-
Expose the certified dataset SHA-256 and gate production on the served identity可能已有人在做 @MaxGhenis 于 1 天前认领。 未关闭
难度 4/5 3-5 天 新手友好度 48/100
PolicyEngine/policyengine-sim-api#742 ·
维护者通常 1 天内回复
-
Update policyengine to 6.2.6可能已有人在做 @policyengine 于 2 天前认领。 未关闭
难度 1/5 1 小时以内 新手友好度 12/100
PolicyEngine/policyengine-sim-api#738 ·
维护者通常 1 天内回复
-
Update policyengine to 6.2.4可能已有人在做 @policyengine 于 3 天前认领。 未关闭
难度 1/5 1 小时以内 新手友好度 15/100
PolicyEngine/policyengine-sim-api#736 ·
维护者通常 1 天内回复
查看 PolicyEngine/policyengine-sim-api 的全部 Issue
相似的 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 84/100
huggingface/smolagents#2976 ·
维护者通常 1 天内回复
-
bug Triage-Needed
难度 2/5 1-3 小时 新手友好度 70/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 66/100
FuRongJun-1999/dsh-memory#170 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
pgvector/pgvector-python#163 ·
-
难度 1/5 1 小时以内 新手友好度 82/100
521xueweihan/HelloGitHub#3940 ·