CodeSampleX

Recordsgolangcloud.google.com/go/pubsub

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 versionv1.0.1
Filter Runtimego 1.26 Architecturex64 Execution contextgo libcglibc Clear filters
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 13 · Steady 1

First observed break

v1.0.1

linux · go@1.26

1 FAIL · stage: UNKNOWN · fingerprint: sha256:17cff61c5997552bd29d6577c0cf7028f4815a1cebc8a523d818a08a19872d82

Library Version Health Measured there Projects
cloud.google.com/go v0.45.1 CANDIDATE Correlated change; unproven combination contract passed 1 project-day
cloud.google.com/go v0.46.3 CANDIDATE Correlated change; unproven combination contract passed 17 project-days
github.com/golang/protobuf v1.3.2 CANDIDATE Correlated change; unproven combination contract passed 18 project-days
github.com/google/go-cmp v0.3.0 CANDIDATE Correlated change; unproven combination contract passed 18 project-days
golang.org/x/oauth2 v0.0.0-20190604053449-0f29369cfe45 CANDIDATE Correlated change; unproven combination contract passed 18 project-days
golang.org/x/sync v0.0.0-20190423024810-112230192c58 CANDIDATE Correlated change; unproven combination contract passed 18 project-days
golang.org/x/time v0.0.0-20190308202827-9d24e82272b4 CANDIDATE Correlated change; unproven combination nothing measured 18 project-days
google.golang.org/api v0.13.0 CANDIDATE Correlated change; unproven combination contract passed 12 project-days
google.golang.org/api v0.9.0 CANDIDATE Correlated change; unproven combination contract passed 6 project-days
google.golang.org/genproto v0.0.0-20190819201941-24fa4b261c55 CANDIDATE Correlated change; unproven combination contract passed 1 project-day
google.golang.org/genproto v0.0.0-20190911173649-1774047e7e51 CANDIDATE Correlated change; unproven combination contract passed 5 project-days
google.golang.org/genproto v0.0.0-20191108220845-16a3f7862a1a CANDIDATE Correlated change; unproven combination contract passed 12 project-days
google.golang.org/grpc v1.21.1 CANDIDATE Correlated change; unproven combination contract passed 18 project-days
github.com/googleapis/gax-go/v2 v2.0.5 PASS All observations passed contract passed 18 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.

Moved: 9 · unchanged at every release: 1

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.