CodeSampleX

Recordsgolanggolang.org/x/termfailure issue

Failure signature

UNKNOWN exit 1 Evidence gap ×1

# example.com/sample/test · test/contract.go:<n>:<n>: dur.UnmarshalText undefined (type caddy.Duration has no field or method UnmarshalText)

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

sha256:2470d64a481a…

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.42.0v0.40.0v0.30.0v0.22.0v0.17.0v0.2.0
golang.org/x/sys v0.43.0 v0.41.0 — v0.22.0 v0.17.0 v0.2.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