Matija Vižintin

@klauspost Are there any plans to implement a fallback to (Un)MarshalText?

In this case we have 2 go apps talking to each other via gRPC on port 8525. Each app sits on it's own (well, hundreds of them) physical machine. So...

hey @msherif1234 I didn't have time (well, it was never prioritized) to work on that, we kept the RTT feature off and it's working fine. So lets close it for...

Well, it turns out is not that hard. I had to replace the RingBuffer with PerfEvent Array in the ebpf code, remove the fentry which is not supported yet and...

It was a fun one and I learned something new :) I would say yes. I did it in a hackish way because I needed to prove that it works...

@msherif1234 That's true, however the code will already throw an error here https://github.com/netobserv/netobserv-ebpf-agent/blob/main/pkg/ebpf/tracer.go#L738 even before falling back https://github.com/netobserv/netobserv-ebpf-agent/blob/main/pkg/ebpf/tracer.go#L172 At least that's the case for x86. Yeah, saw the performance impact...

@msherif1234 sorry for the late reply. I applied your changes from https://github.com/netobserv/netobserv-ebpf-agent/pull/374 to my branch and it works well, thanks!

I deploy it via helm chart and it has a hook that fires an upgrade job. However I run it once more and I see still the same: ``` kubectl...

Yes, 25.8 (sorry, made a mistake above). ``` kubectl describe pod redash-test-upgrade-44l6j Name: redash-test-upgrade-44l6j .... Containers: redash-server: Image: redash/redash:25.8.0 Image ID: docker-pullable://redash/redash@sha256:00d813437db59c3214374a64714e6c016831ceb71f93980f35eb51e8e428b4dd Command: /bin/bash /config/install-upgrade.sh upgrade State: Running Limits: memory:...

This was indeed the issue, the 10 minutes timeout. However the upgrade job completed successfully instead of throwing and error. It looks like the script swallows the error. See here...