PolicyEngine / PolicyEngine/microcosm
Preflight summary counter miscounts (prints FAIL=1 with zero failing checks)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 4
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 94
Description
tools/preflight_us_release_gates.py printed Overall: AT_RISK (exit 2) [FAIL=1, AT-RISK=2, clean=0] on a run whose own --json-out records exactly: selection_carryover PASS, zero_support_preview PASS, export_mass_parity_risk AT_RISK, smoke_probe_support PASS — no FAIL, one AT-RISK, three passes. Exit code and JSON are right; the human-readable tally is wrong. Cosmetic but it reads as a failing gate to an operator. Repro inputs: v9.2 feed 61b115c0…, populace main 4746aba.
Contributor 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.
Research direction
Start in tools/preflight_us_release_gates.py and reproduce the reported human-readable summary using the cited v9.2 feed and populace main inputs. Trace how the displayed FAIL and AT-RISK counts are computed, compare them with the --json-out records, and confirm done when the summary reports zero FAIL, one AT-RISK, and three PASS checks while preserving the correct exit code and JSON.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 85/100