Recordsgolanggo.opentelemetry.io/contrib/instrumentation/net/http/otelhttpv0.70.0go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp.NewHandler
Change the conditions
Current conditions
go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp.NewHandler @v0.70.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 (2)
- Project observations
- 2 / 2
- Contract verifications
- 1 / 1
- Independent reporting peers
- 1
- Last recorded
- 2026-09-17
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v0.70.0
linux · go@1.26
1 FAIL
· stage: PROJECT_RESOLVE
· fingerprint: sha256:4c982a152e43e734c654d84887617e4df1a718080bbc91bfba97b3ee9e535ef5
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/felixge/httpsnoop | v1.1.0 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| github.com/stretchr/testify | v1.11.1 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| go.opentelemetry.io/otel | v1.45.0 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| go.opentelemetry.io/otel/metric | v1.45.0 | CANDIDATE Correlated change; unproven combination | builds observed | 2 project-days |
| go.opentelemetry.io/otel/sdk | v1.45.0 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| go.opentelemetry.io/otel/sdk/metric | v1.45.0 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| go.opentelemetry.io/otel/trace | v1.45.0 | 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: 7 · 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
-
observed PROJECT_RESOLVE exit 1 ×1 v0.70.0 os=linux · runtime=go@1.26 go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp.NewHandler sha256:4c982a152e43…<path>:<n>:<n>: missing go.sum entry for module providing package github.com/google/uuid (imported by go.opentelemetry.io/otel/sdk/resource); to add: …go/module · resolve-diagnostic · outer go runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-10 · Last seen: 2026-09-10
-
observed PROJECT_TEST exit 1 ×1 v0.70.0 os=linux · runtime=go@1.26 go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp.NewHandler sha256:00b364355b89…--- FAIL: TestNewHandlerContract (0.00s) · FAIL example.com/otelhttp-sample 0.004sgo/test · test-runner-diagnostic · outer go testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-10 · Last seen: 2026-09-10