Recordsgolanggo.opentelemetry.io/otel/sdkfailure issue
Failure signature
PROJECT_RESOLVE exit 1 ×1
<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: …
Evidence quality: complete · go/module · resolve-diagnostic · outer go run · First recorded: 2026-09-10 · Last seen: 2026-09-10
sha256:4c982a152e43…
go.opentelemetry.io/otel/sdk/trace.NewTracerProvider go.opentelemetry.io/otel/sdk/trace.TracerProvider go.opentelemetry.io/otel/sdk/trace.WithSyncer go.opentelemetry.io/otel/sdk/trace/tracetest.InMemoryExporter go.opentelemetry.io/otel/sdk/trace/tracetest.NewInMemoryExporter
Where it was measured
PASS means the release recorded a passing observation at PROJECT_RESOLVE and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
- v1.47.0 not measured
- v1.46.0 not measured
- v1.45.0 FAIL
- v1.44.0 not measured
- v1.43.0 not measured
- v1.40.0 not measured
Where it reproduced
- os=linux · runtime=go@1.26 ×1 2026-09-10 → 2026-09-10
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.
Moved: 7 · unchanged at every release: 3
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
- No release in this window recorded a passing observation at PROJECT_RESOLVE.
- Releases in this window never measured at PROJECT_RESOLVE: 5
- No failure domain was inferred for this failure.
Published answers for the affected releases
- go.opentelemetry.io/otel/sdk v1.45.0: resource.Merge returns both a populated Resource with an empty SchemaURL and an ErrSchemaURLConflict error when merging resources with conflicting Schema URLs 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/sdk/resource.Mergego.opentelemetry.io/otel/sdk/resource.ErrSchemaURLConflictgo MIT-0 · 2026-08-17
- go.opentelemetry.io/otel/sdk v1.45.0: Span limits drop the newest attributes but drop the oldest events when their respective maximum counts are reached 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. HOWSpanLimitsAttributeCountLimitEventCountLimitgo MIT-0 · 2026-08-17
- go.opentelemetry.io/otel/sdk v1.45.0: SpanFromContext never returns nil on untraced contexts but yields invalid non-recording spans whose IDs format to 32-character and 16-character zero strings rather than empty strings, RecordError does not set error status, and NewSpanContext drops all fields if either TraceID or SpanID is zero 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.SpanFromContextgo.opentelemetry.io/otel/trace.ContextWithSpango.opentelemetry.io/otel/trace.ContextWithRemoteSpanContextgo.opentelemetry.io/otel/trace.WithNewRootgo.opentelemetry.io/otel/trace.NewSpanContextgo.opentelemetry.io/otel/trace.TraceIDFromHexgo.opentelemetry.io/otel/trace.SpanIDFromHexgo.opentelemetry.io/otel/trace.Span.RecordErrorgo MIT-0 · 2026-08-16