Recordsgolanggoogle.golang.org/protobuffailure issue
Failure signature
PROJECT_TEST exit 1 ×1
--- FAIL: TestMarshalOptionsMultilineAndIndent (0.00s) · === RUN TestMarshalOptionsMarshalAppend · --- PASS: TestMarshalOptionsMarshalAppend (0.00s) …
Evidence quality: complete · go/test · test-runner-diagnostic · outer go test · First recorded: 2026-09-02 · Last seen: 2026-09-02
sha256:cc82e17386c1…
Where it was measured
PASS means the release recorded a passing observation at PROJECT_TEST and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
- v1.36.12 PASS 45 passing observations
- v1.36.11 PASS 144 passing observations
- v1.36.10 FAIL
- v1.36.8 not measured
- v1.36.6 PASS 9 passing observations
- v1.36.5 PASS 9 passing observations
Where it reproduced
- os=linux · runtime=go@1.26 ×1 2026-09-02 → 2026-09-02
Nearest known PASS/FAIL boundaries
The two adjacent releases the verdict changes across. Releases nothing measured do not close the gap; they are counted instead.
-
Last passing release v1.36.6 → first failing release v1.36.10
Releases between them never measured at this stage: 1
What differs across the boundary
- github.com/golang/protobuf v1.5.0, v1.5.4 → v1.5.0, v1.5.3, v1.5.4 hypothesis
- github.com/google/go-cmp v0.5.5, v0.5.9, v0.7.0 → v0.7.0 hypothesis
A version that moved across the boundary is a candidate, not a cause. Only a receipt that recorded the failure and the tree it resolved in the same run is marked as evidence.
-
Last failing release v1.36.10 → first passing release v1.36.11
Both trees resolved every dependency to the same version. Nothing here moved.
Dependency versions across releases
What each release of this package resolved its children to. A child whose version moved is listed first: that is where an upgrade changed something underneath you.
| Library | v1.36.12 | v1.36.11 | v1.36.10 | v1.36.6 | v1.36.5 |
|---|---|---|---|---|---|
| github.com/golang/protobuf | v1.5.2 | v1.5.3 | v1.5.4 | v1.5.4 | v1.5.4 |
| github.com/google/go-cmp | v0.7.0 | v0.7.0 | v0.7.0 | v0.7.0 | v0.6.0 |
Moved: 2 · unchanged at every release: 0
An edge records that a resolver placed one release beside another on a real machine. It is not a claim that the two work together; that question is answered by samples and contracts, not by presence here.
Evidence gaps
- Releases in this window never measured at PROJECT_TEST: 1
- No failure domain was inferred for this failure.
Published answers for the affected releases
- google.golang.org/protobuf v1.36.10: protojson.MarshalOptions This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWprotojson.MarshalOptionsgo MIT-0 · 2026-09-02
- google.golang.org/protobuf v1.36.10: protojson.UnmarshalOptions This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWprotojson.UnmarshalOptionsgo MIT-0 · 2026-09-02
- google.golang.org/protobuf v1.36.10 This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOW MIT-0 · 2026-08-27