Florian Lehner

Closing this PR as superseeded by https://github.com/florianl/go-conntrack/commit/2b1c41ba4c95b66d3d2039c58847bbff973bc8e8.

Just my personal point of view and also with https://github.com/cilium/ebpf/pull/818#issuecomment-1316890797 in mind: `perf` and `ebpf` are two very different subsystems of the Linux kernel. Both together enable very interesting use...

There is ongoing work, around https://github.com/open-telemetry/opentelemetry-collector/pull/10375, to bring the new OTel profiling signal into the OTel collector.

@abhinav or @JacobOaks or @r-hang with https://github.com/uber-go/zap/pull/1429/commits/126ea63be89efd6961a7678da70689e64fabe35f I have moved the test to guarantee compatability to a dedicated sub test. Please let me know, if this works for you.

friendly ping to @abhinav or @JacobOaks or @r-hang - do you have some feedback?

Thanks for your contribution. Without further context it is hard to make a good judgement on the PR. Is there a specific problem you want to address or run into?...

Closing PR due to missing respond.

This is the example from the [Go specification](https://go.dev/ref/spec#Return_statements) (last example in the `Return statements` section): ``` func f(n int) (res int, err error) { if _, err := f(n-1); err...

To help reviewing this PR: Only changes in `Makefile` and `versions.yaml` are hand made. All other code changes are auto generated by `make sync`.

@open-telemetry/profiling-maintainers the PR got updated to only contain the frame types.