Recordsgolanggithub.com/google/martian/v3failure 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=0x6ab1d7] …
Evidence quality: complete · go · unclassified-diagnostic · outer go run · gap stage-unknown · First recorded: 2026-09-19 · Last seen: 2026-09-19
sha256:5fbaa62bfaf3…
github.com/google/martian/v3.Init github.com/google/martian/v3.NewContext github.com/google/martian/v3.NewMultiError github.com/google/martian/v3.NewProxy github.com/google/martian/v3.Noop github.com/google/martian/v3.RequestModifierFunc github.com/google/martian/v3.ResponseModifierFunc
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.
- v3.0.0 FAIL
Where it reproduced
- os=linux · runtime=go@1.26 ×1 2026-09-19 → 2026-09-19
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.
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.
- No failure domain was inferred for this failure.
Published answers for the affected releases
- github.com/google/martian/v3 v3.0.0 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. HOWgo 1.26.6 MIT-0 · 2026-10-19