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.
The cube reads the newest 6 versions and the first 10 symbols of each, so an empty cell here can mean "outside that window" rather than "never measured".
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.50.0
linux · go@1.26
1 FAIL
· stage: UNKNOWN
· fingerprint: sha256:253d5d5b625b3969008b36ff2a40556b3337059f5216b6f2aa910dfd2c09055e
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| cloud.google.com/go/bigquery | v1.3.0 | CANDIDATE Correlated change; unproven combination | builds observed | 3 project-days |
| cloud.google.com/go/datastore | v1.0.0 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| cloud.google.com/go/pubsub | v1.1.0 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| cloud.google.com/go/storage | v1.5.0 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| github.com/golang/mock | v1.3.1 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| github.com/golang/protobuf | v1.3.2 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| github.com/google/go-cmp | v0.3.1 | CANDIDATE Correlated change; unproven combination | nothing measured | 3 project-days |
| github.com/google/pprof | v0.0.0-20190515194954-54271f7e092f | CANDIDATE Correlated change; unproven combination | nothing measured | 3 project-days |
| github.com/googleapis/gax-go/v2 | v2.0.5 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| github.com/jstemmer/go-junit-report | v0.9.1 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| golang.org/x/exp | v0.0.0-20191227195350-da58074b4299 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| golang.org/x/lint | v0.0.0-20191125180803-fdd1cda4f05f | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| golang.org/x/net | v0.0.0-20191209160850-c0dbc17a3553 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| golang.org/x/oauth2 | v0.0.0-20191202225959-858c2ad4c8b6 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| golang.org/x/text | v0.3.2 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| golang.org/x/tools | v0.0.0-20191227053925-7b8e75db28f4 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| google.golang.org/api | v0.15.0 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| google.golang.org/genproto | v0.0.0-20191230161307-f3c370f40bfb | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| google.golang.org/grpc | v1.26.0 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| honnef.co/go/tools | v0.0.1-2019.2.3 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| github.com/google/martian | v2.1.0+incompatible | UNKNOWN No linked outcome measured | nothing measured | 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: 24 · unchanged at every release: 8
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.