CodeSampleX

Recordsgolanggolang.org/x/termv0.41.0term.Terminal.SetSize

Change the conditions
Fixed
OSdebian glibc Symbolterm.Terminal.SetSize
Filter Runtimego 1.26 Package versionv0.41.0 Architecturex64 Package managergo Execution contextgo libcglibc Clear filters

Current conditions

term.Terminal.SetSize @v0.41.0debian glibc · x64 · go 1.26 · go · go

1 of 1 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate came back clean (1)

Project observations
1 / 1
Contract verifications
1 / 1
Independent reporting peers
1
Last recorded
2026-10-14
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 0

First observed break

v0.41.0

linux · go@1.26

2 FAIL · stage: PROJECT_COMPILE · fingerprint: sha256:7343982f90b77447bd3953ebffac1a2859dffe4f94ab28fc2486a9d4c1b8d527

View exact conditions View failure cluster
Library Version Health Measured there Projects
golang.org/x/sys v0.42.0 CANDIDATE Correlated change; unproven combination contract passed 2 project-days

The measured column is about each dependency's own release, not about the pair. A resolver placing two releases side by side is not evidence that they work together.

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.22.0v0.17.0v0.2.0v0.0.0-20210927222741-03fcf44c2211v0.0.0-20201126162022-7de9c90e9dd1
golang.org/x/sys v0.47.0 v0.45.0 v0.44.0 v0.42.0 v0.41.0 v0.22.0 v0.17.0 v0.2.0 v0.0.0-20210615035016-665e8c7367d1 v0.47.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.

Recent failure clusters