Recordsgolangcloud.google.com/gofailure issue
Failure signature
UNKNOWN exit 1 Evidence gap ×1
panic: runtime error: invalid memory address or nil pointer dereference · [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x783c57] …
Evidence quality: complete · go · unclassified-diagnostic · outer go run · gap stage-unknown · First recorded: 2026-10-18 · Last seen: 2026-10-18
sha256:23fa82d9b00b…
Where it was measured
PASS means the release recorded a passing observation at UNKNOWN and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
- v0.62.0 not measured
- v0.57.0 not measured
- v0.56.0 not measured
- v0.52.0 FAIL
- v0.50.0 not measured
- v0.46.3 not measured
- v0.44.1 not measured
Where it reproduced
- os=linux · runtime=go@1.26 ×1 2026-10-18 → 2026-10-18
Nearest known PASS/FAIL boundaries
No release either side of this failure recorded a passing observation at this stage, so where it starts and stops is not established.
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.
Moved: 19 · unchanged at every release: 7
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
- The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
- The captured output could not establish: stage-unknown.
- No release in this window recorded a passing observation at UNKNOWN.
- Releases in this window never measured at UNKNOWN: 6
- No failure domain was inferred for this failure.
Published answers for the affected releases
No published sample names these releases.