CodeSampleX

Recordsgolanggolang.org/x/termfailure issue

Failure signature

UNKNOWN exit 1 EOF Evidence gap ×1

FAIL: expected second ReadLine to return (<str>, nil), got (<str>, EOF) · exit status 1

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

sha256:a5ae7352d0f9…

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

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.30.0v0.22.0v0.17.0v0.2.0v0.0.0-20210927222741-03fcf44c2211v0.0.0-20201126162022-7de9c90e9dd1v0.0.0-20201117132131-f5c789dd3221
golang.org/x/sys — v0.22.0 v0.17.0 v0.2.0 v0.0.0-20210615035016-665e8c7367d1 v0.8.0 v0.0.0-20191026070338-33540a1f6037

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