Bug trace/telemetry

[sergeyseliverstovv]

Hi. There are problems with trace in new versions of Sponge. In this file https://github.com/go-dev-frame/sponge/blob/main/pkg/tracer/resource.go there is an import of URL Schema version 1.24. When trace is enabled, panic occurs: conflicting Schema URL: https://opentelemetry.io/schemas/1.26.0 and https://opentelemetry.io/schemas/1.24.0. URL Schema conflict. Apparently, you need to fix the import so that it refers to URL Schema version 1.26. Then everything works and panic does not occur. Apparently, the library https://pkg.go.dev/go.opentelemetry.io/otel/sdk takes the schema version 1.26 and your code takes version 1.24. Because of this, a conflict occurs.

To reproduce the error, you need to enable trace (enableTrace = true). Add URL and port for jaeger and start the service. It will crash with panic:

panic: conflicting Schema URL: https://opentelemetry.io/schemas/1.26.0 and https://opentelemetry.io/schemas/1.24.0.

OS: Linux
Version Sponge: 1.12.8
Version Go: 1.24
Version telemetry:
go.opentelemetry.io/auto/sdk v1.1.0 // indirect

go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc v0.49.0 // indirect

go.opentelemetry.io/otel v1.34.0 // indirect

go.opentelemetry.io/otel/exporters/jaeger v1.17.0 // indirect

go.opentelemetry.io/otel/exporters/stdout/stdouttrace v1.24.0 // indirect

go.opentelemetry.io/otel/metric v1.34.0 // indirect

go.opentelemetry.io/otel/sdk v1.34.0 // indirect

go.opentelemetry.io/otel/trace v1.34.0 // indirect

[zhufuyi]

OK, change go.opentelemetry.io/otel/trace and go.opentelemetry.io/otel/sdk to v1.26.0 in the next version.