CodeSampleX

Recordsgolanggolang.org/x/modfailure issue

Failure signature

UNKNOWN exit 1 Evidence gap ×3

# golang.org/x/tools/internal/tokeninternal · <path>:<n>:<n>: invalid array length -delta * delta (constant -256 of type int64)

Evidence quality: complete · go · unclassified-diagnostic · outer go run · gap stage-unknown · First recorded: 2026-09-19 · Last seen: 2026-09-19

sha256:7e561a3b135b…

Where it was measured

PASS means the release recorded a passing observation at UNKNOWN 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.

Libraryv0.18.0v0.13.0v0.8.0v0.6.0-dev.0.20220419223038-86c51ed26bb4v0.6.0-dev.0.20220106191415-9b9b3d81d5e3
golang.org/x/tools v0.22.0 v0.14.0 v0.1.12 v0.1.12 —
golang.org/x/crypto — — — v0.3.0 —

Moved: 1 · 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

No published sample names these releases.

Back to the package