CodeSampleX

Recordsgolanggo.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpcv1.43.0go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc.WithCompressor

Change the conditions
Fixed
Runtimenode 22 Package versionv1.43.0 Symbolgo.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc.WithCompressor
Filter OSubuntu glibc Architecturex64 Package managernpm 10 Execution contextnode libcglibc Clear filters

Current conditions

go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc.WithCompressor @v1.43.0ubuntu glibc · x64 · node 22 · npm 10 · node

0 of 5 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate failed

Project observations
nothing at this coordinate
Contract verifications
0 / 5
Last recorded
2026-09-08

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 14 · Steady 2

First observed break

v1.43.0

linux

14 FAIL · stage: PROCESS_START · fingerprint: sha256:c12549970456efb5abdc90b679695c6689107d4f097d612245d6bfb25e01ec32

Library Version Health Measured there Projects
github.com/stretchr/testify v1.11.1 CANDIDATE Correlated change; unproven combination contract passed 9 project-days
go.opentelemetry.io/otel v1.43.0 CANDIDATE Correlated change; unproven combination contract passed 9 project-days
go.opentelemetry.io/otel/exporters/otlp/otlptrace v1.43.0 CANDIDATE Correlated change; unproven combination contract passed 9 project-days
go.opentelemetry.io/otel/metric v1.43.0 CANDIDATE Correlated change; unproven combination contract passed 9 project-days
go.opentelemetry.io/otel/sdk v1.43.0 CANDIDATE Correlated change; unproven combination contract passed 9 project-days
go.opentelemetry.io/otel/sdk/metric v1.43.0 CANDIDATE Correlated change; unproven combination contract passed 9 project-days
go.opentelemetry.io/otel/trace v1.43.0 CANDIDATE Correlated change; unproven combination contract passed 9 project-days
go.opentelemetry.io/proto/otlp v1.10.0 CANDIDATE Correlated change; unproven combination contract passed 9 project-days
google.golang.org/genproto/googleapis/rpc v0.0.0-20260401024825-9d38bb4040a9 CANDIDATE Correlated change; unproven combination contract passed 6 project-days
google.golang.org/genproto/googleapis/rpc v0.0.0-20260406210006-6f92a3bedf2d 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.80.0 CANDIDATE Correlated change; unproven combination contract passed 7 project-days
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 9 project-days
github.com/cenkalti/backoff/v5 v5.0.3 PASS All observations passed contract passed 9 project-days
go.uber.org/goleak v1.3.0 PASS All observations passed contract passed 7 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: 11 · unchanged at every release: 4

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.

Recent failure clusters