Recordsgolanggo.opentelemetry.io/otel/tracev1.24.0ParseTraceState
Change the conditions
Current conditions
ParseTraceState @v1.24.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-15
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v1.24.0
linux · go@1.26
1 FAIL
· stage: PROJECT_COMPILE
· fingerprint: sha256:c0d74feba02d3894f68403449d50b78248a06b341a11abdd653086f4ebb4ac8e
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/google/go-cmp | v0.6.0 | CANDIDATE Correlated change; unproven combination | contract passed | 29 project-days |
| github.com/stretchr/testify | v1.8.4 | CANDIDATE Correlated change; unproven combination | contract passed | 29 project-days |
| go.opentelemetry.io/otel | v1.24.0 | CANDIDATE Correlated change; unproven combination | contract passed | 29 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.
| Library | v1.46.0 | v1.45.0 | v1.44.0 | v1.43.0 | v1.37.0 | v1.35.0 | v1.34.0 | v1.28.0 | v1.24.0 |
|---|---|---|---|---|---|---|---|---|---|
| github.com/google/go-cmp | v0.7.0 | v0.7.0 | v0.7.0 | v0.7.0 | v0.7.0 | v0.7.0 | v0.6.0 | — | v0.6.0 |
| github.com/stretchr/testify | v1.12.1 | v1.11.1 | v1.11.1 | v1.11.1 | v1.11.1 | v1.10.0 | — | — | v1.8.4 |
| go.opentelemetry.io/otel | v1.46.0 | v1.45.0 | v1.44.0 | v1.43.0 | v1.37.0 | v1.35.0 | v1.34.0 | v1.28.0 | v1.24.0 |
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
-
observed PROJECT_COMPILE exit 1 ×1 v1.24.0 os=linux · runtime=go@1.26 sha256:c0d74feba02d…<path> declared and not used: tsInv · <path> declared and not used: tsNoKey · <path> declared and not used: tsDupgo/compiler · compiler-diagnostic · outer go runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-03 · Last seen: 2026-09-03
-
observed PROJECT_TEST exit 1 ×1 v1.24.0 os=linux · runtime=go@1.26 sha256:fcb97af2b71c…--- FAIL: TestNewSpanContext_DropsFieldsWhenTraceIDOrSpanIDIsZero (0.00s) …go/test · test-runner-diagnostic · outer go testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-03 · Last seen: 2026-09-03
-
observed UNKNOWN exit 1 Evidence gap ×1 v1.24.0 os=linux · runtime=go@1.26 sha256:5751bc248e71…test/contract.go:<n>:<n>: found packages main (main.go) and sample (tracestate.go) in <path> …go · unclassified-diagnostic · outer go run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-03 · Last seen: 2026-09-03Diagnostic re-verification candidate