CodeSampleX

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/KimMachineGun/automemlimit/memlimit (imported by github.<token>); to add: …

Evidence quality: complete · go/module · resolve-diagnostic · outer go run · First recorded: 2026-08-29 · Last seen: 2026-08-29

sha256:0facb7ea8a74…

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

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.

Libraryv2.4.4v2.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

Published answers for the affected releases

Back to the package