CodeSampleX

Recordsgolangcloud.google.com/go/longrunning

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.9.0 Symbolwhole package
Filter Runtimego 1.26 Architecturex64 Execution contextgo Clear filters
OS × Package manager
1 1○ 12026-10-14
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 0

First observed break

v0.9.0

linux · go@1.26

2 FAIL · stage: UNKNOWN · fingerprint: sha256:7c7eeb6a2fd81719cc4da0b8eacd8bbae318e65039c150c79b8aee8829ea1114

Library Version Health Measured there Projects
cloud.google.com/go v0.123.0 CANDIDATE Correlated change; unproven combination contract passed 3 project-days
github.com/googleapis/gax-go/v2 v2.20.0 CANDIDATE Correlated change; unproven combination builds observed 1 project-day
github.com/googleapis/gax-go/v2 v2.22.0 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
google.golang.org/api v0.273.1 CANDIDATE Correlated change; unproven combination contract passed 1 project-day
google.golang.org/api v0.277.0 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
google.golang.org/genproto v0.0.0-20260319201613-d00831a3d3e7 CANDIDATE Correlated change; unproven combination builds observed 3 project-days
google.golang.org/genproto/googleapis/api v0.0.0-20260401001100-f93e5f3e9f0f CANDIDATE Correlated change; unproven combination builds observed 1 project-day
google.golang.org/genproto/googleapis/api v0.0.0-20260406210006-6f92a3bedf2d CANDIDATE Correlated change; unproven combination contract passed 2 project-days
google.golang.org/genproto/googleapis/rpc v0.0.0-20260401001100-f93e5f3e9f0f CANDIDATE Correlated change; unproven combination contract passed 1 project-day
google.golang.org/genproto/googleapis/rpc v0.0.0-20260427160629-7cedc36a6bc4 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
google.golang.org/grpc v1.79.3 CANDIDATE Correlated change; unproven combination contract passed 1 project-day
google.golang.org/grpc v1.81.0 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
google.golang.org/protobuf v1.36.11 CANDIDATE Correlated change; unproven combination contract passed 3 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: 8 · unchanged at every release: 3

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.