CodeSampleX

Recordsgolanggo.opentelemetry.io/otel/exporters/stdout/stdoutlogfailure issue

Failure signature

UNKNOWN exit 1 Evidence gap ×1

unexpected Body in output: map[Type:String Value:sample message] · exit status 1

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

sha256:4df12764c585…

go.opentelemetry.io/otel/exporters/stdout/stdoutlog.Exporter go.opentelemetry.io/otel/exporters/stdout/stdoutlog.New go.opentelemetry.io/otel/exporters/stdout/stdoutlog.Option go.opentelemetry.io/otel/exporters/stdout/stdoutlog.WithPrettyPrint go.opentelemetry.io/otel/exporters/stdout/stdoutlog.WithWriter go.opentelemetry.io/otel/exporters/stdout/stdoutlog.WithoutTimestamps

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: 3 · unchanged at every release: 6

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