Recordsgolanggo.opentelemetry.io/otel/tracefailure issue
Failure signature
UNKNOWN exit 1 Evidence gap ×1
# command-line-arguments · <path> cannot call pointer method Len on <str>.Set
Evidence quality: complete · go · unclassified-diagnostic · outer go run · gap stage-unknown · First recorded: 2026-09-19 · Last seen: 2026-09-19
sha256:da1f6bbc4f06…
go.opentelemetry.io/otel/trace.NewTracerConfig go.opentelemetry.io/otel/trace.TracerOption go.opentelemetry.io/otel/trace.WithInstrumentationAttributeSet go.opentelemetry.io/otel/trace.WithInstrumentationAttributes go.opentelemetry.io/otel/trace.WithInstrumentationVersion go.opentelemetry.io/otel/trace.WithSchemaURL
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.46.0 not measured
- v1.45.0 not measured
- v1.44.0 FAIL
- v1.43.0 not measured
- v1.39.0 not measured
- v1.37.0 not measured
Where it reproduced
- os=linux · runtime=go@1.26 ×1 2026-09-19 → 2026-09-19
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.46.0 | v1.45.0 | v1.44.0 | v1.43.0 | v1.39.0 | v1.37.0 |
|---|---|---|---|---|---|---|
| github.com/stretchr/testify | v1.12.1 | v1.11.1 | v1.11.1 | v1.11.1 | — | v1.11.1 |
| go.opentelemetry.io/otel | v1.46.0 | v1.45.0 | v1.44.0 | v1.43.0 | v1.39.0 | v1.37.0 |
| github.com/google/go-cmp | v0.7.0 | v0.7.0 | v0.7.0 | v0.7.0 | v0.7.0 | v0.7.0 |
Moved: 2 · unchanged at every release: 1
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: 5
- No failure domain was inferred for this failure.
Published answers for the affected releases
- go.opentelemetry.io/otel/trace v1.44.0: SpanContextConfig 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/trace.SpanContextConfiggo 1.26.6 MIT-0 · 2026-09-19
- go.opentelemetry.io/otel/trace v1.44.0: FlagsSampled 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/trace.FlagsSampledgo 1.26.6 MIT-0 · 2026-09-19
- go.opentelemetry.io/otel/trace v1.44.0: TracerOption 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/trace.TracerOptiongo 1.26.6 MIT-0 · 2026-09-19