Robert Pająk

@utezduyar protobuf dependencies are needed as `otlptracehttp` is basically profobuf over HTTP. The issue is that gRPC dependencies should not be present. EDIT: TBH I am shocked that `go build`...

@utezduyar The payload send via HTTP is serialized using [protobuf](https://protobuf.dev/) .

Related issues: - https://github.com/open-telemetry/opentelemetry-go/pull/4353#discussion_r1272180864 - https://github.com/open-telemetry/opentelemetry-go/pull/4353#discussion_r1272220665 Side note: The processing logic may be implemented similarly to `PeriodicReader`.

> It seems like that comment needs to rephrased to communicate to the user of the interface (not the implementer). I disagree. The interface should communicate the contract for the...

@Kaushal28 I guess it is about Asynchronous instruments callbacks. @MadVikingGod am I correct? This issue has been assigned to [Go: Metric SDK (Post-GA)](https://github.com/orgs/open-telemetry/projects/35) and I am not sure if it...

Jaeger exporter is removed. Please use OTLP exporter instead.

@Kaushal28 Can you review https://github.com/open-telemetry/opentelemetry-go/pull/3989 and https://github.com/open-telemetry/opentelemetry-go/pull/3990? When I reproduced the problem(s) it was easier for me to try to fix them, but I would appreciate your reviews.

@bboreham Can you please check https://github.com/open-telemetry/opentelemetry-go/issues/2793#issuecomment-1866427747?

AFAIK all code generation is now automated.

The `OTEL_RESOURCE_ATTRIBUTES` env var is still still not properly parsed. It accepts keys that should not be allowed. They values are not precent decoded as noted https://github.com/open-telemetry/opentelemetry-dotnet/issues/3395#issuecomment-1200526391 Reference: https://www.w3.org/TR/baggage/#definition