Recordsgolanggolang.org/x/crypto/x509roots/fallbackfailure issue
Failure signature
PROJECT_TEST exit 1 ×1
--- FAIL: TestPathAndMethodMatchers (0.00s) · panic: interface conversion: interface {} is nil, not *caddy.Replacer [recovered, repanicked] …
Evidence quality: complete · go/test · test-runner-diagnostic · outer go test · First recorded: 2026-08-29 · Last seen: 2026-08-29
sha256:dda800f87ad3…
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.
- v0.0.0-20260213171211-a408498e5541 FAIL
- v0.0.0-20250305170421-49bf5b80c810 PASS 5 passing observations
Where it reproduced
- os=linux · runtime=go@1.26 ×1 2026-08-29 → 2026-08-29
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 v0.0.0-20250305170421-49bf5b80c810 → first failing release v0.0.0-20260213171211-a408498e5541
Both trees resolved every dependency to the same version. Nothing here moved.
Evidence gaps
- No failure domain was inferred for this failure.
Published answers for the affected releases
- golang.org/x/crypto/x509roots/fallback v0.0.0-20260213171211-a408498e5541: iterate NSS root certificates and construct x509 cert pool with constraints using bundle.Roots 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. HOWgolang.org/x/crypto/x509roots/fallback/bundle.Roots MIT-0 · 2026-08-28