Cijo Thomas

Samplers too?

Looks like same issue in HTTP also https://github.com/open-telemetry/opentelemetry-rust/blob/main/opentelemetry-otlp/src/exporter/http/mod.rs#L271

> .and_then(|g| match &*g { > Some(client) => Ok(Arc::clone(client)), > _ => Err(OTelSdkError::AlreadyShutdown), > })?; if the guard is dropped here itself, then yes, this looks correct. (I was incorrectly...

Can you share a minimal repro of the shutdown issue? (do include the cargo.toml file as well so we can which the feature flags that are active.)

I think we need to start tracking all issues blocking OpenTelemetry in wasm using a label, and see where we stand. I won't be surprised if OpenTelemetry Rust is completely...

Closing inactive PRs. The linked issue can be used to track the work of supporting wasm in general.

Questionable APIs are now moved to experimental_feature flags, and that is the extent of what we plan for the coming release.

> [@cijothomas](https://github.com/cijothomas) Do we need to remove dropped_attribute_counts from [proto file](https://github.com/open-telemetry/opentelemetry-proto/blob/6c98d1576f13d9115e03d0a484d2f9e1a7293608/opentelemetry/proto/trace/v1/trace.proto#L269) too, right? No. dropped_counts can remain everywhere, except in the `opentelemetry` crate.

I think there is a confusion about this item, let me clarify: Dropped counts is a valid thing - it should be enforced, and should be exported in the otlp...

> The problem is that libraries in the exporter network stack enter `tracing` spans of their own (normally on debug or tracing level), these go to the global subscriber, and...