CodeSampleX

Recordsgolanggo.opentelemetry.io/otel/sdkfailure issue

Failure signature

UNKNOWN exit 1 Evidence gap ×1

unexpected resource.New error: error detecting resource: conflicting Schema URL: <url> and <url> · exit status 1

Evidence quality: complete · go · unclassified-diagnostic · outer go run · gap stage-unknown · First recorded: 2026-10-14 · Last seen: 2026-10-14

sha256:b2204a91efd4…

go.opentelemetry.io/otel/sdk/resource.Empty go.opentelemetry.io/otel/sdk/resource.ErrSchemaURLConflict go.opentelemetry.io/otel/sdk/resource.Merge go.opentelemetry.io/otel/sdk/resource.New go.opentelemetry.io/otel/sdk/resource.NewWithAttributes go.opentelemetry.io/otel/sdk/resource.Resource go.opentelemetry.io/otel/sdk/resource.WithOSType go.opentelemetry.io/otel/sdk/resource.WithSchemaURL go.opentelemetry.io/otel/sdk/resource.WithTelemetrySDK

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.

Where it reproduced

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

Published answers for the affected releases

Back to the package