CodeSampleX

Recordsgolanggo.opentelemetry.io/proto/otlpv1.9.0go.opentelemetry.io/proto/otlp/common/v1.AnyValue_IntValue

Change the conditions
Fixed
OSdebian glibc Symbolgo.opentelemetry.io/proto/otlp/common/v1.AnyValue_IntValue
Filter Runtimego 1.26 Package versionv1.9.0 Architecturex64 Package managergo Execution contextgo libcglibc Clear filters

Current conditions

go.opentelemetry.io/proto/otlp/common/v1.AnyValue_IntValue @v1.9.0debian glibc · x64 · go 1.26 · go · go

1 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 came back clean (1)

Project observations
1 / 1
Contract verifications
1 / 1
Independent reporting peers
1
Last recorded
2026-09-17

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 5 · Steady 0

First observed break

v1.9.0

linux · go@1.26

1 FAIL · stage: PROJECT_RESOLVE · fingerprint: sha256:913c4fa8708f6f223542f30d24ef4740c3b52fdb3e23e45d54d05ad7e5d3ed16

Library Version Health Measured there Projects
github.com/grpc-ecosystem/grpc-gateway/v2 v2.27.2 CANDIDATE Correlated change; unproven combination nothing measured 23 project-days
google.golang.org/grpc v1.75.1 CANDIDATE Correlated change; unproven combination contract passed 23 project-days
google.golang.org/protobuf v1.36.10 CANDIDATE Correlated change; unproven combination contract passed 16 project-days
google.golang.org/protobuf v1.36.11 CANDIDATE Correlated change; unproven combination contract passed 5 project-days
google.golang.org/protobuf v1.36.12 CANDIDATE Correlated change; unproven combination contract passed 2 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