CodeSampleX

Recordsgolanggo.opentelemetry.io/otel/logv0.19.0go.opentelemetry.io/otel/log.EnabledParameters

Change the conditions
Fixed
Package versionv0.19.0 Symbolgo.opentelemetry.io/otel/log.EnabledParameters libcglibc
Filter OSubuntu glibc Runtimego 1.26 Architecturex64 Package managergo 1 Clear filters

Current conditions

go.opentelemetry.io/otel/log.EnabledParameters @v0.19.0ubuntu glibc · x64 · go 1.26 · go 1

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
15 / 19
Contract verifications
0 / 5
Independent reporting peers
1
Last recorded
2026-09-01

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 2 · Steady 4

First observed break

v0.19.0

linux · node@22.23 · moduleSystem=cjs · executionContext=node

11 FAIL · stage: UNKNOWN · fingerprint: sha256:9be950af9140edade9f2c5aa029896fb7dd194960195369ee277ef42a11d6868

Library Version Health Measured there Projects
go.opentelemetry.io/otel v1.43.0 CANDIDATE Correlated change; unproven combination contract passed 24 project-days
go.opentelemetry.io/otel v1.46.0 CANDIDATE Correlated change; unproven combination contract passed 1 project-day
github.com/go-logr/logr v1.4.3 PASS All observations passed contract passed 23 project-days
github.com/go-logr/logr v1.4.4 PASS All observations passed contract passed 2 project-days
github.com/stretchr/testify v1.11.1 PASS All observations passed contract passed 24 project-days
github.com/stretchr/testify v1.12.1 PASS All observations passed builds observed 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: 1 · 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.

Recent failure clusters

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