Recordsgolanggithub.com/go-stack/stackfailure issue
Failure signature
PROJECT_COMPILE exit 1 ×1
test/contract.go:<n>:<n>: undefined: scep.BadCertId (but have BadCertID)
Evidence quality: complete · go/compiler · compiler-diagnostic · outer go run · First recorded: 2026-08-30 · Last seen: 2026-08-30
sha256:0110984809f1…
Where it was measured
PASS means the release recorded a passing observation at PROJECT_COMPILE and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
Where it reproduced
- os=linux · runtime=go@1.26 ×1 2026-08-30 → 2026-08-30
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
- No release in this window recorded a passing observation at PROJECT_COMPILE.
- Releases in this window never measured at PROJECT_COMPILE: 2
- No failure domain was inferred for this failure.
Published answers for the affected releases
- github.com/go-stack/stack v1.6.0: capture and format call stack and caller frames with stack.Caller and stack.Trace 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. HOWstack.Callerstack.Tracego 1.26.6 MIT-0 · 2026-08-28