CodeSampleX

Recordsgolanggolang.org/x/net

Compatibility cube

Pick any two dimensions as axes; everything else becomes a filter. Clicking a cell pins its slice and drills one level deeper.

Fixed
Package versionv0.0.0-20220403103023-749bd193bc2b
Filter Architecturex64 Clear filters
Symbol × Runtime
4 12026-09-03

Showing the environments with the most evidence. The cube reads the newest 6 versions and the first 10 symbols of each, so an empty cell here can mean "outside that window" rather than "never measured".

How to read the grid

Reading a cell: The number is how many recorded observations the rate divides — one build files an observation per stage it reached, so it counts neither builds nor machines nor people. The document beside it is a different fact from a different source: whether a sample exists at that coordinate, and how our own run of it went there.

  • no sample at this coordinate yet
  • there is a sample here, and nothing of ours has run it at this coordinate yet
  • there is a sample here, and our run of it at this coordinate came back clean
  • there is a sample here, and our run of it at this coordinate failed
  • there is a sample here, and this coordinate records both a passing and a failing run of it
  • nothing recorded — unknown, never "works" and never "broken"
  • there is a level below this cell — click to open it

A document means there is a sample at that coordinate. Whether one EXISTS is a fact about this release and this API and does not change with OS, runtime or package manager; its COLOUR is how that sample ran in the environment you are looking at.

Cells are aggregates of everything still varying in this slice (the n/m count says how much). Click one to pin its coordinates and see the next level.

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 4 · Steady 0

First observed break

v0.0.0-20220403103023-749bd193bc2b

linux

31 FAIL · stage: UNKNOWN · fingerprint: sha256:9be950af9140edade9f2c5aa029896fb7dd194960195369ee277ef42a11d6868

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.58.0v0.57.0v0.55.0v0.53.0v0.52.0v0.51.0v0.50.0v0.37.0v0.35.0v0.34.0v0.29.0v0.21.0v0.17.0v0.12.0v0.4.0v0.0.0-20210525063256-abc453219eb5v0.0.0-20200625001655-4c5254603344
golang.org/x/crypto v0.55.0 v0.54.0 v0.52.0 v0.50.0 v0.49.0 v0.48.0 v0.48.0 v0.36.0 v0.33.0 v0.32.0 v0.27.0 v0.20.0 v0.14.0 v0.11.0 v0.0.0-20200622213623-75b288015ac9
golang.org/x/sys v0.47.0 v0.47.0 v0.45.0 v0.44.0 v0.42.0 v0.41.0 v0.41.0 v0.31.0 v0.30.0 v0.29.0 v0.25.0 v0.17.0 v0.13.0 v0.10.0 v0.47.0 v0.47.0 v0.0.0-20210603081109-ebe580a85c40
golang.org/x/term v0.45.0 v0.45.0 v0.43.0 v0.42.0 v0.41.0 v0.40.0 v0.40.0 v0.30.0 v0.29.0 v0.28.0 v0.24.0 v0.17.0 v0.13.0 v0.10.0 v0.0.0-20201126162022-7de9c90e9dd1
golang.org/x/text v0.41.0 v0.40.0 v0.37.0 v0.36.0 v0.35.0 v0.34.0 v0.34.0 v0.23.0 v0.22.0 v0.21.0 v0.18.0 v0.14.0 v0.13.0 v0.11.0 v0.5.0 v0.3.6 v0.3.2

Moved: 4 · 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.