You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
config: a .nan value is reported twice by the settings validator #1050
Found in job 022's security review (a note, not a blocker for #998).
A budget or cap written as .nan produces two issues from validate_document — one from the zero/ceiling shape walk and one from the whole-number check — where every other invalid form produces one. Measured: .nan → 2 issues, .inf → 1.
The consequence is a count an operator cannot reconcile (settings invalid: 2 issues for a single wrong value) and a validator whose issue list is not one-per-defect.
What it needs
Decide which rule owns the NaN case and make the other skip it, so one bad value is one issue.
A test pinning the count for .nan, .inf, -1, 1e40 and a quoted "NaN", so the one-per-defect property is asserted rather than assumed.
Measured in 022-settings-ceiling's round-2/review-security.md.
Activity