CodeSampleX

Recordsgolanggithub.com/prometheus/client_model

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
Package versionv0.6.1 Symbolgithub.com/prometheus/client_model/go.Bucket
Filter Runtimego 1.26 Architecturex64 Execution contextgo libcglibc Clear filters
OS × Package manager
1○ 12026-09-17
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.1

linux · go@1.26

1 FAIL · stage: PROJECT_RESOLVE · fingerprint: sha256:41c0bdc4aec8568b43c029357bc89b673b870e4168177a899c9eb8bfaab5e79c

Library Version Health Measured there Projects
google.golang.org/protobuf v1.33.0 CANDIDATE Correlated change; unproven combination contract passed 8 project-days
google.golang.org/protobuf v1.34.2 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
google.golang.org/protobuf v1.36.12 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.6.3v0.6.2v0.6.1v0.5.0v0.2.0v0.0.0-20190812154241-14fe0d1b01d4
github.com/golang/protobuf — — — — v1.5.4 v1.3.5
google.golang.org/protobuf v1.36.12 v1.36.6 v1.36.12 v1.35.1 — —

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