Proof Portal

Projects

jsonparser

ProbeLabs36 findings · 123 requirements
SYS-REQ-052SystemReview

When ArrayEach iterates a well-formed array and the Get call for an element returns an error (e.g., due to a truncated element within the array), ArrayEach shall propagate that error to the caller rather than silently continuing iteration.

PriorityshallTypeguaranteeCategoryfunctionalComponentparserAssuranceEFindingsnone open

Specification

The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.

Description

When ArrayEach iterates a well-formed array and the Get call for an element returns an error (e.g., due to a truncated element within the array), ArrayEach shall propagate that error to the caller rather than silently continuing iteration.

FRETish formula
the parser shall always satisfy !array_callback_returns_error | array_callback_error_is_propagated

Rationale & tags

Why this requirement exists, and how it is categorised.

ArrayEach error propagation from element-level Get failures is a distinct contract from ObjectEach callback error propagation (SYS-REQ-032) and from malformed-array input (SYS-REQ-029).

arrayeachcallbackerror-propagation

Verification & provenance

How this requirement was checked: the review trail, edit history, and the machine-analysis status terms (each ⓘ explains what it means).

Assurance levelE
Formalizationvalid
Realizabilityrealizable
Vacuitychecked_ok
Strategyfretish

Review

Status
approved
Reviewer
human:leonidbugaev
Reviewed
Apr 23, 2026, 00:00 UTC

History

Created
Apr 14, 2026, 18:00 UTC · agent:claude
Modified
Jul 26, 2026, 14:54 UTC · human:cli

Obligations

What this requirement must witness to be considered satisfied — the required evidence, and the tests that discharge each one.

1 obligation · 1 discharged

Browse the catalogue
Discharged
Worst case if violatedCritical

ArrayEach silently continues iteration after a Get error returns a stale (value,offset) pair; the next loop iteration dereferences data[offset] past EOF, panicking with index-out-of-range.

Discharging evidence1/1 required witnessed
  • nominalrequiredpresent
    Covered by 1 test

Formula evidence

The formal formula behind this requirement, the variables it is written over, and the tests that exercise it (each term is explained inline).

FRETish formula

the parser shall always satisfy !array_callback_returns_error | array_callback_error_is_propagated

Variables

NameTypeDirectionDescription
array_callback_returns_errorTrue when the Get call for an array element within ArrayEach returns an error.
array_callback_error_is_propagatedTrue when ArrayEach propagates the element-level Get error to the caller.

Witnesses· 3 scenarios total

  • TestArrayEachCallbackReceivesElementError
    deep_spec_test.go:1134exercises 1 condition scenario
  • TestArrayEachCallbackErrorNotSwallowed
    deep_spec_test.go:1163exercises 1 condition scenario
  • TestArrayEachErrorPropagation
    deep_spec_test.go:392
  • TestMCDC_SYS_REQ_052_Row1_TriggerFalse
    mcdc_spec_witnesses_test.go:1841exercises 1 condition scenario
  • TestObligation_SYS_REQ_052
    obligation_evidence_test.go:427

Its place

This requirement shown inside its trace neighbourhood — the parents it satisfies, the code and tests attached to it, and its findings.

Loading graph…

Trace evidence

The concrete artifacts linked to this requirement — implementing code, verifying tests, documents, and the findings raised against it.

Impact

Blast radius — if you change this requirement, what else may need re-checking, and what it in turn depends on.

If you change this

Requirements
0
Files
2
Tests
3
At-risk contracts
0

Files to re-check (2)

  • aliases.goaliases.go
  • parser.goparser.go

Tests to re-run (3)

  • deep_spec_test.godeep_spec_test.go
  • mcdc_spec_witnesses_test.gomcdc_spec_witnesses_test.go
  • obligation_evidence_test.goobligation_evidence_test.go

What this rests on

Discussions

Discuss this with the proof team. Nothing changes in your audit automatically — you open a request and a staff member records any outcome inside the thread.

Sign in to discuss this with the proof team.Sign in