Robert Pająk

How is it supposed to be triggered? Notice ``` on: push: tags: - v1.* workflow_dispatch: ```

> I think it is ok for this PR to just enable the summary feature. Can you please showcase what would be the output on a fork?

> I cannot trigger the benchmark CI on this PR, Cannot you do it on your fork? https://github.com/XSAM/opentelemetry-go/tree/summary-for-benchmark

> Could you please provide us with any documentation or knowledge regarding how OpenTelemetry manages memory? I think it would be an overkill. You can always read the codebase. >...

Closing per previous comment.

For me it looks like a correct usage of OTel Metrics SDK.

> that code should return 7 and true This is correct. From https://www.compart.com/en/unicode/U+FFFD: > UTF-8 Encoding: 0xEF 0xBF 0xBD

@MrAlias, PTAL

Another problem is that the usage of `WalkAttributes` can lead to a deadlock or even panic. E.g. if one to tries to use any of the record's method in the...

This is not a stable JSON representation. See https://pkg.go.dev/go.opentelemetry.io/otel/exporters/stdout/stdoutlog#pkg-overview: > it does not provide an interchange format for OpenTelemetry that is supported with any stability or compatibility guarantees However, it...