Recordsgolanggo.opentelemetry.io/otelfailure issue
Failure signature
UNKNOWN exit 1 Evidence gap ×1
# sample/test · test/contract.go:<n>:<n>: cannot call pointer method Len on <str>.Set · test/contract.go:<n>:<n>: cannot call pointer method Len on <str>.Set
Evidence quality: complete · go · unclassified-diagnostic · outer go run · gap stage-unknown · First recorded: 2026-09-16 · Last seen: 2026-09-16
sha256:61579858e38a…
go.opentelemetry.io/otel/attribute.Int go.opentelemetry.io/otel/attribute.Key go.opentelemetry.io/otel/attribute.KeyValue go.opentelemetry.io/otel/attribute.String
Where it was measured
PASS means the release recorded a passing observation at UNKNOWN and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
- v1.45.0 not measured
- v1.44.0 not measured
- v1.43.0 not measured
- v1.37.0 FAIL
- v1.35.0 not measured
- v1.34.0 not measured
- v1.32.0 not measured
Where it reproduced
- os=linux · runtime=go@1.26 ×1 2026-09-16 → 2026-09-16
Nearest known PASS/FAIL boundaries
No release either side of this failure recorded a passing observation at this stage, so where it starts and stops is not established.
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.45.0 | v1.44.0 | v1.43.0 | v1.37.0 | v1.35.0 | v1.34.0 | v1.32.0 |
|---|---|---|---|---|---|---|---|
| github.com/go-logr/logr | v1.4.4 | v1.4.3 | v1.4.4 | v1.4.3 | v1.4.2 | v1.4.2 | — |
| github.com/google/go-cmp | v0.7.0 | v0.7.0 | v0.7.0 | v0.7.0 | v0.7.0 | v0.6.0 | — |
| github.com/stretchr/testify | v1.11.1 | v1.11.1 | v1.11.1 | v1.11.1 | v1.10.0 | — | — |
| go.opentelemetry.io/auto/sdk | v1.2.1 | v1.2.1 | v1.2.1 | v1.1.0 | v1.1.0 | v1.1.0 | — |
| go.opentelemetry.io/otel/metric | v1.45.0 | v1.44.0 | v1.43.0 | v1.37.0 | v1.35.0 | v1.34.0 | — |
| go.opentelemetry.io/otel/trace | v1.45.0 | v1.44.0 | v1.43.0 | v1.37.0 | v1.35.0 | v1.34.0 | — |
| github.com/cespare/xxhash/v2 | v2.3.0 | v2.3.0 | v2.3.0 | — | — | — | — |
| github.com/go-logr/stdr | v1.2.2 | v1.2.2 | v1.2.2 | v1.2.2 | v1.2.2 | v1.2.2 | — |
Moved: 6 · 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.
Evidence gaps
- The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
- The captured output could not establish: stage-unknown.
- No release in this window recorded a passing observation at UNKNOWN.
- Releases in this window never measured at UNKNOWN: 6
- No failure domain was inferred for this failure.
Published answers for the affected releases
- go.opentelemetry.io/otel v1.37.0: attribute.FLOAT64 This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWgo.opentelemetry.io/otel/attribute.FLOAT64 MIT-0 · 2026-09-16
- go.opentelemetry.io/otel v1.37.0: attribute.STRING This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWgo.opentelemetry.io/otel/attribute.STRING MIT-0 · 2026-09-16
- go.opentelemetry.io/otel v1.37.0: attribute.KeyValue This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWgo.opentelemetry.io/otel/attribute.KeyValue MIT-0 · 2026-09-16