CodeSampleX

Recordsgolanggithub.com/google/s2a-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.

Fixed
Package versionv0.1.9 Package managergo 1
Filter Runtimego 1.26 Symbolwhole package libcglibc Clear filters
OS × Architecture
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 17 · Unknown 3 · Steady 12

First observed break

v0.1.9

linux · go@1.26

1 FAIL · stage: UNKNOWN · fingerprint: sha256:f3a5a30110770e510159fdb2eda104f320d4f31f36251c1770da6e4ec58af6d8

Library Version Health Measured there Projects
github.com/google/go-cmp v0.7.0 CANDIDATE Correlated change; unproven combination contract passed 64 project-days
golang.org/x/crypto v0.47.0 CANDIDATE Correlated change; unproven combination contract passed 21 project-days
golang.org/x/crypto v0.49.0 CANDIDATE Correlated change; unproven combination contract passed 11 project-days
golang.org/x/crypto v0.52.0 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
golang.org/x/crypto v0.53.0 CANDIDATE Correlated change; unproven combination contract passed 9 project-days
golang.org/x/crypto v0.55.0 CANDIDATE Correlated change; unproven combination contract passed 20 project-days
google.golang.org/grpc v1.78.0 CANDIDATE Correlated change; unproven combination contract passed 19 project-days
google.golang.org/grpc v1.79.2 CANDIDATE Correlated change; unproven combination contract passed 1 project-day
google.golang.org/grpc v1.79.3 CANDIDATE Correlated change; unproven combination contract passed 5 project-days
google.golang.org/grpc v1.80.0 CANDIDATE Correlated change; unproven combination contract passed 6 project-days
google.golang.org/grpc v1.81.0 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
google.golang.org/grpc v1.82.0 CANDIDATE Correlated change; unproven combination contract passed 7 project-days
google.golang.org/grpc v1.82.1 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
google.golang.org/grpc v1.83.2 CANDIDATE Correlated change; unproven combination contract passed 21 project-days
google.golang.org/grpc v1.84.0 CANDIDATE Correlated change; unproven combination contract passed 1 project-day
google.golang.org/protobuf v1.36.11 CANDIDATE Correlated change; unproven combination contract passed 63 project-days
google.golang.org/protobuf v1.36.12 CANDIDATE Correlated change; unproven combination contract passed 1 project-day
cloud.google.com/go/translate v1.10.3 UNKNOWN No linked outcome measured nothing measured 11 project-days
cloud.google.com/go/translate v1.12.7 UNKNOWN No linked outcome measured nothing measured 8 project-days
google.golang.org/appengine v1.6.8 UNKNOWN No linked outcome measured nothing measured 13 project-days
golang.org/x/sync v0.19.0 PASS All observations passed builds observed 21 project-days
golang.org/x/sync v0.20.0 PASS All observations passed contract passed 13 project-days
golang.org/x/sync v0.21.0 PASS All observations passed contract passed 9 project-days
golang.org/x/sync v0.22.0 PASS All observations passed contract passed 20 project-days
google.golang.org/api v0.264.0 PASS All observations passed contract passed 19 project-days
google.golang.org/api v0.272.0 PASS All observations passed contract passed 1 project-day
google.golang.org/api v0.273.1 PASS All observations passed contract passed 5 project-days
google.golang.org/api v0.274.0 PASS All observations passed contract passed 6 project-days
google.golang.org/api v0.277.0 PASS All observations passed contract passed 2 project-days
google.golang.org/api v0.287.1 PASS All observations passed contract passed 10 project-days
google.golang.org/api v0.288.0 PASS All observations passed contract passed 20 project-days
google.golang.org/api v0.293.0 PASS All observations passed contract passed 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: 4 · unchanged at every release: 5

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.