Alexey Alexandrov

Since a typical Node.js program is full of async execution, the profiler stacks may look confusing as the current stack does not contain the stack of the call that actually...

Consistently use int64 type for string refs in pprofextended.

1

Fixing two fields that used a different type, I don't think there is a good reason to be inconsistent.

In pprofextended proto, consider moving Location.type_index to Mapping

4

We define it as ``` // Type of frame (e.g. kernel, native, python, hotspot, php). Index into string table. uint32 type_index = 6; ``` I can't easily think of a...

Reordering things: ``` message Sample { repeated uint64 location_index = 1; repeated int64 value = 2; repeated Label label = 3; // fields 4, 5, 6 are missing. uint64 locations_start_index...

"go test ./..." fails when llvm-symbolizer is not available (even if llvm-symbolizer-14 is there)

3

#891 added support for populating function start lines using llvm-symbolizer data. One caveat is that if llvm-symbolizer is not available, the default `go test ./...` run fails with the error...

Add doc_url field to match its recent addition in pprof proto.

1

google/pprof/pull/888 added this field in pprof proto, this change adds it to the OTel profiling proto to match the change.