CodeSampleX

Recordsgolanggolang.org/x/mod

there is a sample for this release and API (1)

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
OSlinux Package versionv0.40.0 Symbolgolang.org/x/mod/modfile.Require
Filter Runtimego 1.26 Architecturex64 Execution contextgo Clear filters
OS × Package manager
1 12026-09-07
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 3 · Steady 0

First observed break

v0.6.0-dev.0.20220106191415-9b9b3d81d5e3

linux

7 FAIL · stage: PROJECT_PROCESS

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.39.0v0.38.0v0.37.0v0.35.0v0.24.0v0.18.0v0.13.0v0.8.0v0.6.0-dev.0.20220419223038-86c51ed26bb4v0.3.0v0.1.1-0.20191105210325-c90efee705ee
golang.org/x/crypto v0.3.0 v0.0.0-20200622213623-75b288015ac9 v0.0.0-20191011191535-87dc89f01550
golang.org/x/tools v0.49.0 v0.48.0 v0.47.0 v0.44.0 v0.13.0 v0.22.0 v0.14.0 v0.6.0 v0.1.12 v0.0.0-20200825202427-b303f430e36d
golang.org/x/xerrors v0.0.0-20200804184101-5ec99f83aff1 v0.0.0-20191011141410-1b5146add898

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