Recordsgolanggithub.com/go-logr/logrfailure issue
Failure signature
PROJECT_COMPILE exit 1 ×1
<path> undefined: log.KeyValue · <path> undefined: log.StringValue
Evidence quality: complete · go/compiler · compiler-diagnostic · outer go test · First recorded: 2026-08-31 · Last seen: 2026-08-31
sha256:10769dcea866…
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-31 → 2026-08-31
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 v1.4.3 → first failing release v1.4.4
Both trees resolved every dependency to the same version. Nothing here moved.
Evidence gaps
- 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-logr/logr v1.4.4: Logger, Logger.Info, Logger.WithValues 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. HOWlogr.Loggerlogr.Logger.Infologr.Logger.WithValues MIT-0 · 2026-08-18