hiroto.toyoda 1ebdc06c18 feat(tracing): surface otel shutdown errors via --debug ...

OTel SDK/exporter errors already go through docker/cli's own
otel.SetErrorHandler(debug.OTELErrorHandler), installed by the plugin
framework at startup. Our own handler, installed at package init time,
was always clobbered before any command ran (plugin.Run() sets its handler
after all inits execute), so it never had any effect - verified by tracing
the exact call order and reproducing the flag behavior against a built
binary.

Drop that dead handler along with the COMPOSE_OTEL_DEBUG env var it
introduced. The one genuinely-discarded error (the tracer shutdown/flush
error in wrapRunE) now goes through logrus like everything else in the
codebase: it's already gated by --debug/-D via logrus's own level, so no
explicit check is needed.

Signed-off-by: hiroto.toyoda <[email protected]>

2026-09-02 17:12:12 +02:00

..

cmd_span_test.go

golangci-lint: use gci formatter instead of goimports

2025-12-01 12:21:50 +01:00

cmd_span.go

feat(tracing): surface otel shutdown errors via --debug

2026-09-02 17:12:12 +02:00