Recordsgolanggo.yaml.in/yaml/v2failure 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.
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.
Dependency versions across releases
What each release of this package resolved its children to. A child whose version moved is listed first: that is where an upgrade changed something underneath you.
| Library | v2.4.4 | v2.4.2 |
|---|---|---|
| gopkg.in/check.v1 | — | v0.0.0-20161208181325-20d25e280405 |
Moved: 0 · unchanged at every release: 1
An edge records that a resolver placed one release beside another on a real machine. It is not a claim that the two work together; that question is answered by samples and contracts, not by presence here.
Evidence gaps
- No release in this window recorded a passing observation at PROJECT_RESOLVE.
- Releases in this window never measured at PROJECT_RESOLVE: 2
- No failure domain was inferred for this failure.
Published answers for the affected releases
No published sample names these releases.