yzhao

> @yzhao1012 thanks, good comments! I addressed all current comments, if you have more please feel free to add them. Thanks for the quick actions. I am testing this PR...

Patch in the following diff to fix a GCC build failure. We have a gcc build pipeline to validate the c++ code with gcc compiler (in addition to the default...

@oazizi000 merged this PR in https://github.com/pixie-io/pixie/commit/cf3f844d8f6d7460517ca895243226ff804d1247. Close. I am working on pulling in the docker images produced by dockerfile into native bazel py3_image. After that, @orishuss can add bpf tests...

(Yaxiong from Pixie team) Sorry for late reply. I think you are already played with the existing Pixie profiler: https://docs.pixielabs.ai/tutorials/profiler/ (it does not support Java application profiling, but only the...

Yaxiong from the Pixie team: Did you by any chance collect the description (`kubectl describe pod ...`) of the pods, and the logs (`kubectl logs ...`) when you noticed this...

(Yaxiong from the Pixie team) Thanks for reporting this! `src/stirling/scripts/stirling_wrapper.sh` wraps `bazel` (build system used by Pixie codebase). It seems your bazel configuration has problem. Could you run: ``` bazel...

Run ``` make buildifier ``` To reform the build file. The Jenkins failure is because of BUILD.bazel file's line's ordering are not sorted according to the style guide.

@orishuss from Groundcover is working on a c-gRPC library tracing. Ori feel free to provide updates to @MrSupiri yourself.

You seem are running stirling_wrapper? Could you confirm what exactly you did to run it? (yaml file, exact kubectl command etc., ideally someone can reproduce it without chances of mistakes)...

Thanks @harold-kfuse ! > > Looks like a parse failure. Tagging @yzhao1012 on this issue. Maybe he could help take a look and debug the issue. > > @chengruizhe Should...