Lalit Kumar Bhasin

@RazvanRotari Thanks for the PR. Can you also add tests to validate this? There are some relevant unit-tests here - [test_serde](https://github.com/open-telemetry/opentelemetry-rust/blob/ad990d6d33aa73b35e0e3b792b1fe3ea4251b92b/opentelemetry-otlp/tests/integration_test/tests/traces.rs#L90) if that helps.

> @lalitb @cijothomas Looks like the latest `cc` crate [can't be built](https://github.com/open-telemetry/opentelemetry-rust/actions/runs/9848718542/job/27191173814?pr=1906) with rustc 1.65. Should it be fixed (pinned, I assume?) here or in a separate PR? I think...

@stormshield-fabs I took the liberty of fixing minor merge conflicts in this PR, as it was introduced by changes from my own PR. Hope that's fine :)

@thomasameisel Do you have the stack trace for all other threads at the time when Thread1 was waiting for the lock ?

Thanks @thomasameisel the other thread stack would have given more insight of any deadlock situation or if other thread has invoked any LogManager operation which is taking too much of...

@nishchith-cp - Is it possible to get the stack trace of all other threads, not just the thread crashing with timeout. There is a deadlock scenario between threads, so the...

> When opentelemetry used as a layer with global tracing subscriber it is now impossible to shutdown properly (it only decrements a reference, but doesn't execute Drop). That's expected behavior....

> If current behavior (no shutdown if there are other references) is intentional and should remain, then I think it'd be helpful to change the documentation (explicitly state that it's...

To clarify, the `shutdown_tracer_provider` will eventually be removed from the API surface. Alternatively, it might be moved to the SDK and renamed to `release_tracer_provider`, as its primary purpose is to...

Specifying constants as field names - I believe this is valid question, probably better to be asked in the tokio tracing repo? There are no examples with tracing integration in...