CodeSampleX

Recordsgolanggolang.org/x/termfailure issue

Failure signature

PROJECT_COMPILE exit 1 ×2

test/contract.go:<n>:<n>: cannot use d.out.ReadFrom(bytes.NewReader(p)) (value of type int64) as int value in return statement

Evidence quality: complete · go/compiler · compiler-diagnostic · outer go run · First recorded: 2026-10-14 · Last seen: 2026-10-14

sha256:7343982f90b7…

golang.org/x/term.IsTerminal golang.org/x/term.NewTerminal

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.

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.45.0v0.43.0v0.42.0v0.41.0v0.40.0v0.30.0
golang.org/x/sys v0.47.0 v0.45.0 v0.44.0 v0.42.0 v0.41.0 —

Moved: 1 · unchanged at every release: 0

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