CodeSampleX

Recordsgolanggithub.com/smallstep/scepfailure 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…

github.com/smallstep/scep.BadAlg github.com/smallstep/scep.BadCertId github.com/smallstep/scep.BadMessageCheck github.com/smallstep/scep.BadRequest github.com/smallstep/scep.BadTime github.com/smallstep/scep.CertRep github.com/smallstep/scep.FAILURE github.com/smallstep/scep.FailInfo github.com/smallstep/scep.NewCSRRequest github.com/smallstep/scep.PKCSReq github.com/smallstep/scep.PKIMessage github.com/smallstep/scep.ParsePKIMessage github.com/smallstep/scep.WithCACerts github.com/smallstep/scep/x509util.CertificateRequest github.com/smallstep/scep/x509util.CreateCertificateRequest

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

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

Published answers for the affected releases

Back to the package