CodeSampleX

Recordsgolanggo.opentelemetry.io/proto/otlpv1.10.0go.opentelemetry.io/proto/otlp/collector/logs/v1.ExportLogsServiceResponse

Change the conditions
Fixed
Package versionv1.10.0 Symbolgo.opentelemetry.io/proto/otlp/collector/logs/v1.ExportLogsServiceResponse libcglibc
Filter OSubuntu glibc Runtimego 1.26 Architecturex64 Package managergo 1 Clear filters

Current conditions

go.opentelemetry.io/proto/otlp/collector/logs/v1.ExportLogsServiceResponse @v1.10.0ubuntu glibc · x64 · go 1.26 · go 1

0 of 1 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
22 / 23
Contract verifications
0 / 1
Independent reporting peers
2
Last recorded
2026-09-07

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 5 · Steady 0

First observed break

v1.10.0

linux

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

Library Version Health Measured there Projects
github.com/grpc-ecosystem/grpc-gateway/v2 v2.28.0 CANDIDATE Correlated change; unproven combination contract passed 35 project-days
google.golang.org/grpc v1.79.2 CANDIDATE Correlated change; unproven combination contract passed 4 project-days
google.golang.org/grpc v1.80.0 CANDIDATE Correlated change; unproven combination contract passed 29 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 35 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: 3 · unchanged at every release: 0

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

Showing the 12 most-reported of 41 recorded failure clusters. The rest are single reports.