You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice if we could change the API to be forced to pass a type from the otel-sdk crate somewhere to ensure we get a compile-error when there is a version mismatch.
Currently, things will just silently break if you bump one version but not the other :(
The text was updated successfully, but these errors were encountered:
thomaseizinger
changed the title
Compile-time link to the right OTEL version
Compile-time enforce to the right OTEL version
Mar 7, 2024
This silent failure caused us to have issues for a while. We've been trying to figure out a way to enforce this at compile time (or allow the user to pass in a specific OtelData TypeId, but it's difficult without tracing-subscriber changes. Curious to hear if you resolved in another way (we just bumped version on our fork).
This silent failure caused us to have issues for a while. We've been trying to figure out a way to enforce this at compile time (or allow the user to pass in a specific OtelData TypeId, but it's difficult without tracing-subscriber changes. Curious to hear if you resolved in another way (we just bumped version on our fork).
I played around with this for a while but also couldn't get anything meaningful to work. So far, I've enforced it manually in the dependency bumps.
It would be nice if we could change the API to be forced to pass a type from the otel-sdk crate somewhere to ensure we get a compile-error when there is a version mismatch.
Currently, things will just silently break if you bump one version but not the other :(
The text was updated successfully, but these errors were encountered: