Restore Scotland population live coverage with the fixed PolicyEngine bundle
Maintainers usually reply within 1 day
Nobody has claimed this yet.
- #3877 by @anth-volk — closed without merging
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start by reviewing the Scotland live test and local request-contract parametrization in the API project, plus its dependency declarations and lockfile; the issue does not give their file paths. Check dependency resolution for policyengine[models]==6.2.3 before the existing simulation-API support check, then follow the stated upstream release and worker qualification sequence. Done means the restored live test passes against the deployed staging candidate without skipping it or weakening its success assertions.
Written by the indexing model from the issue text.
Description
Restore the Scotland population live test and its local request-contract parametrization removed by #3875, and upgrade API v1 to the published policyengine==6.2.3 release containing PolicyEngine/policyengine.py#565.
Implementation PR: #3877, rebased onto master after #3875 merged. The exact test cases are restored, both project and generic Dockerfile pin policyengine[models]==6.2.3, and the authentic PyPI lockfile is regenerated. uv lock --check now passes, including with the Cloud Run image's uv 0.12.1.
Local validation against installed 6.2.3: 266 focused tests pass on Python 3.12 and 3.14; configured mypy passes for 97 source files; 10 live tests collect, including Scotland population and household checks. Formatting, lint, workflow syntax, migration checks, changelog, and whitespace pass.
Remaining dependency: merge and deploy PolicyEngine/policyengine-sim-api#733 (tracking PolicyEngine/policyengine-sim-api#732), qualify the worker, and verify 6.2.3 in the simulation gateway's version response. API v1's worker-support check must remain blocking until that deployment is complete. Then pass API CI and the restored Scotland population test against the deployed staging candidate before promotion. Collection or local request-contract tests do not establish deployed simulation success.
- Dominant language
- Python
- Stars
- 18
- Forks
- 33
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 20
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from PolicyEngine/policyengine-api
-
State society-wide reports run on the sparse national datasetPossibly taken @anth-volk claimed this 4 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 35/100
PolicyEngine/policyengine-api#3864 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 38/100
PolicyEngine/policyengine-api#3823 ·
Maintainers usually reply within 1 day
-
API v2: report validations as an append-only, provenance-keyed resource on reportsMay be free again @anth-volk claimed this 32 days ago, and no pull request is open. Open
PolicyEngine/policyengine-api#3818 · 1 assignee ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
PolicyEngine/policyengine-api#3816 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
PolicyEngine/policyengine-api#3814 ·
Maintainers usually reply within 1 day
All issues in PolicyEngine/policyengine-api
Similar issues
-
[BUG] Container scenario crashes without expected_recovery_time, kube DNS example uses retry_waitOpenneeds-triage
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
krkn-chaos/krkn#1627 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
NousResearch/hermes-agent#136483 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
[BUG] LazyStackedTensorDictStore zeroes the last byte of a new key set on the last elementPossibly taken @peterdsharpe claimed this today. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
pytorch/tensordict#2307 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day