Recordsgolanggithub.com/go-logr/stdrfailure issue
Failure signature
PROJECT_TEST Evidence gap ×20
Evidence quality: legacy-evidence-incomplete · First recorded: 2026-08-17 · Last seen: 2026-08-20
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.
- v1.2.2 FAIL
Where it reproduced
- os=windows · runtime=go@1.26 ×19 2026-08-17 → 2026-08-17
- os=linux · runtime=go@1.26 ×1 2026-08-20 → 2026-08-20
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.
- No release in this window recorded a passing observation at PROJECT_TEST.
- No failure domain was inferred for this failure.
Published answers for the affected releases
- github.com/go-logr/stdr v1.2.2: Create a logr.Logger using stdr.New with stdlib log.Logger and verify Info/Error logging 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. HOWstdr.New MIT-0 · 2026-08-18