Recordsgolangcloud.google.com/go
no sample at this coordinate yet
Compatibility cube
Pick any two dimensions as axes; everything else becomes a filter. Clicking a cell pins its slice and drills one level deeper.
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
First observed break
v0.57.0
linux · go@1.26
2 FAIL
· stage: PROJECT_RESOLVE
· fingerprint: sha256:960c448010d338b23e4225acf905c3ba5fc46c4e38004ca42dccb0ec225d0a82
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| cloud.google.com/go/bigquery | v1.8.0 | CANDIDATE Correlated change; unproven combination | builds observed | 1 project-day |
| cloud.google.com/go/pubsub | v1.3.1 | CANDIDATE Correlated change; unproven combination | builds observed | 1 project-day |
| cloud.google.com/go/storage | v1.10.0 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| github.com/golang/mock | v1.4.3 | CANDIDATE Correlated change; unproven combination | builds observed | 1 project-day |
| github.com/golang/protobuf | v1.4.2 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| github.com/google/go-cmp | v0.4.1 | CANDIDATE Correlated change; unproven combination | builds observed | 1 project-day |
| github.com/google/pprof | v0.0.0-20200430221834-fc25d7d30c6d | CANDIDATE Correlated change; unproven combination | builds observed | 1 project-day |
| github.com/googleapis/gax-go/v2 | v2.0.5 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| github.com/jstemmer/go-junit-report | v0.9.1 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| golang.org/x/lint | v0.0.0-20200302205851-738671d3881b | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| golang.org/x/net | v0.0.0-20200520182314-0ba52f642ac2 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| golang.org/x/oauth2 | v0.0.0-20200107190931-bf48bf16ab8d | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| golang.org/x/text | v0.3.2 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| golang.org/x/tools | v0.0.0-20200618134242-20370b0cb4b2 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| google.golang.org/api | v0.28.0 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| google.golang.org/genproto | v0.0.0-20200618031413-b414f8b61790 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| google.golang.org/grpc | v1.29.1 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| honnef.co/go/tools | v0.0.1-2020.1.4 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| github.com/google/martian | v2.1.0+incompatible | UNKNOWN No linked outcome measured | nothing measured | 1 project-day |
| cloud.google.com/go/datastore | v1.1.0 | PASS All observations passed | builds observed | 1 project-day |
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: 19 · unchanged at every release: 11
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.