no python symbolization (and no profiles for python 3.14)

[aubergenepizza]

I am running some workloads that use python 3.14, and I see no profiles for them in the system.
The issue seems to be missing definitions for 3.14 here: https://github.com/coroot/pyroscope/blob/main/ebpf/python/python_offsets_gen_amd64.go

only error log I found that contains the word python is:

E0611 15:16:11.145837 3459454 python.go:38] pid=2932080 lib=/proc/2932080/root/usr/lib/x86_64-linux-gnu/libpthread.so.0: failed to attach python uprobes: symbol pthread_cond_timedwait not found

[gecube]

The root cause is in the eBPF profiler, not in node-agent itself. node-agent gets its Python unwinder from github.com/grafana/pyroscope/ebpf, which it replaces with the coroot/pyroscope fork (upstream grafana dropped ebpf/ from main). That fork's offset table (pyVersions in ebpf/python/python_offsets_gen_*.go) stops at {3, 13, 0}, so for any 3.14 process GetUserOffsets returns unsupported version — patch-guessing only spans a single major.minor and never crosses a minor boundary. That's why there are no profiles.

The pthread_cond_timedwait not found line is unrelated noise: on glibc ≥ 2.34 that symbol lives in libc.so.6 (the libpthread.so.0 you see is an empty stub), and the thread-lock uprobe still attaches fine via libc.

I opened a fix that adds the CPython 3.14 offsets: coroot/pyroscope#3.

Build & test it right now

The fix lives in the pyroscope fork, so point node-agent's replace at the branch:

git clone https://github.com/coroot/coroot-node-agent && cd coroot-node-agent
go mod edit -replace github.com/grafana/pyroscope/ebpf=github.com/gecube/pyroscope/ebpf@22b69c8c6af69d1a4192eb67239ef8a1639a575c
go mod tidy
# then build the agent image/binary as usual and run it on your node

(Use replace, not go get github.com/gecube/... — the fork keeps the github.com/grafana/pyroscope/ebpf module path.)

How to confirm

Currently a 3.14 process logs:

pyperf get python process data failed  err="unsupported python version ... {3 14 6}"

With the fix the same process logs instead:

pyperf process profiling init success  pid=...  py_data="...Version:{Major:3 Minor:14 Patch:6}..."

and Python frames start showing up. I verified this A/B against a live python:3.14.6 container.

What's next

Once coroot/pyroscope#3 is merged, the replace pin in this repo's go.mod just needs to be bumped to the new fork commit — I'll follow up with that PR.