Recordsgolanggithub.com/cenkalti/backoff/v5failure issue
Failure signature
PROJECT_COMPILE exit 1 ×1
<path> undefined: sdklog.NewBatchingProcessor
Evidence quality: complete · go/compiler · compiler-diagnostic · outer go run · First recorded: 2026-08-30 · Last seen: 2026-08-30
sha256:e2caf4a02af3…
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.
- v5.0.3 FAIL
Where it reproduced
- os=linux · runtime=go@1.26 ×1 2026-08-30 → 2026-08-30
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
- No release in this window recorded a passing observation at PROJECT_COMPILE.
- No failure domain was inferred for this failure.
Published answers for the affected releases
- github.com/cenkalti/backoff/v5 v5.0.3: ConstantBackOff 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. HOWgithub.com/cenkalti/backoff/v5.ConstantBackOff MIT-0 · 2026-09-16
- github.com/cenkalti/backoff/v5 v5.0.3: PermanentError 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. HOWgithub.com/cenkalti/backoff/v5.PermanentError MIT-0 · 2026-09-15
- github.com/cenkalti/backoff/v5 v5.0.3: NewTicker 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. HOWgithub.com/cenkalti/backoff/v5.NewTicker MIT-0 · 2026-09-15