Recordsgolanggithub.com/jackc/puddle/v2failure issue
Failure signature
UNKNOWN exit 1 Evidence gap ×1
panic: interface conversion: interface {} is nil, not *caddy.Replacer · goroutine 1 [running]: …
Evidence quality: complete · go · unclassified-diagnostic · outer go run · gap stage-unknown · First recorded: 2026-08-27 · Last seen: 2026-08-27
sha256:f3a5a3011077…
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.
- v2.2.2 FAIL
Where it reproduced
- os=linux · runtime=go@1.26 ×1 2026-08-27 → 2026-08-27
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/jackc/puddle/v2 v2.2.2: create and manage a generic resource pool with puddle.NewPool 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. HOW MIT-0 · 2026-08-21