Recordsgolanggo.opentelemetry.io/otel/sdk
there is a sample for this release and API (2)
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
v1.43.0
linux
16 FAIL
· stage: PROCESS_START
· fingerprint: sha256:c12549970456efb5abdc90b679695c6689107d4f097d612245d6bfb25e01ec32
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/go-logr/logr | v1.4.3 | CANDIDATE Correlated change; unproven combination | contract passed | 56 project-days |
| github.com/go-logr/logr | v1.4.4 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| github.com/google/go-cmp | v0.7.0 | CANDIDATE Correlated change; unproven combination | contract passed | 55 project-days |
| github.com/stretchr/testify | v1.11.1 | CANDIDATE Correlated change; unproven combination | contract passed | 54 project-days |
| go.opentelemetry.io/otel | v1.43.0 | CANDIDATE Correlated change; unproven combination | contract passed | 57 project-days |
| go.opentelemetry.io/otel/metric | v1.43.0 | CANDIDATE Correlated change; unproven combination | contract passed | 57 project-days |
| go.opentelemetry.io/otel/sdk/metric | v1.42.0 | CANDIDATE Correlated change; unproven combination | builds observed | 5 project-days |
| go.opentelemetry.io/otel/sdk/metric | v1.43.0 | CANDIDATE Correlated change; unproven combination | contract passed | 51 project-days |
| go.opentelemetry.io/otel/trace | v1.43.0 | CANDIDATE Correlated change; unproven combination | contract passed | 57 project-days |
| golang.org/x/sys | v0.42.0 | CANDIDATE Correlated change; unproven combination | contract passed | 54 project-days |
| golang.org/x/sys | v0.45.0 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| golang.org/x/sys | v0.47.0 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| github.com/google/uuid | v1.6.0 | PASS All observations passed | contract passed | 56 project-days |
| go.uber.org/goleak | v1.3.0 | PASS All observations passed | contract passed | 44 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: 2
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.