Recordsgolanggithub.com/rcrowley/go-metricsfailure issue
Failure signature
PROJECT_RESOLVE exit 1 ×1
<path>:<n>:<n>: missing go.sum entry for module providing package github.com/skip2/go-qrcode (imported by github.com/slackhq/nebula/cmd/nebula-cert); to add: …
Evidence quality: complete · go/module · resolve-diagnostic · outer go list · First recorded: 2026-08-31 · Last seen: 2026-08-31
sha256:5008c43f49e4…
Where it was measured
PASS means the release recorded a passing observation at PROJECT_RESOLVE 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-20250401214520-65e299d6c5c9 not measured
- v0.0.0-20201227073835-cf1acfcdf475 FAIL
Where it reproduced
- os=linux · runtime=go@1.26 ×1 2026-08-31 → 2026-08-31
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_RESOLVE.
- Releases in this window never measured at PROJECT_RESOLVE: 1
- No failure domain was inferred for this failure.
Published answers for the affected releases
- github.com/rcrowley/go-metrics v0.0.0-20201227073835-cf1acfcdf475: register and update counter and meter in a go-metrics registry 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. HOWmetrics.NewCountermetrics.NewMetermetrics.NewRegistry MIT-0 · 2026-08-27