Marc Alff

As indicated earlier, `opentelemetry-cpp::otlp_grpc_metrics_exporter` is missing. Please try to add this library, and post the results if still failing, or close the issue.

Accepting this bug to improve logging. Not sure if we can validate every UTF-8 strings, to investigate.

Seen again many times, latest today 2025-10-27: ``` [ RUN ] BasicCurlHttpTests.FinishInAsyncCallback ext/test/http/curl_http_test.cc:645: Failure Value of: handlers[i]->got_response_.load(std::memory_order_acquire) Actual: false Expected: true ``` This test needs to be fixed (preferable), or...

Thanks for the report. Read the docs is definitively out of date. We (opentelemetry-cpp) need to figure out whether to continue using rtd, or to expose the doc in opentelemetry.io....

@gparlamas Can you clarify which exporter the application will use precisely ? The build shows `WITH_OTLP_GRPC=ON`, is this intended ?

@gparlamas Thanks for the details. If using the OTLP GRPC exporter, then yes, this will bring a lot of dependencies due to grpc. I don't have performance numbers to compare,...

@Reneg973 Tip to format all the code (C++, CMake, Bazel): ``` [malff@malff-desktop ~]$ more ~/bin/otel_cf.sh #!/bin/bash podman run --rm --privileged=true --volume ${PWD}:/otel otel/cpp_format_tools ``` See https://github.com/open-telemetry/cpp-build-tools/tree/main/cpp_format_tools

To discuss, file a spec PR to have a common expected behavior, naming parameters, etc, for all repos.

The fact that boolean environment variables have a default of `false` comes from the spec. See this conversation: * https://github.com/open-telemetry/opentelemetry-specification/pull/2755#discussion_r962171923

To investigate, long turn support for platform / compiler not supporting REGEX.