James Bartlett

~~Don't really have context to help with 2, but for your first issue I think you just need to specify a cgo constraint on your custom platform (`"@io_bazel_rules_go//go/toolchain:{cgo_off,cgo_on}"`). I don't...

Hi all, thanks for your patience. With our latest release of Vizier, 0.12.17, we now have early **alpha** support for ARM64. Our testing infrastructure doesn't yet support ARM, so we'd...

Sorry for the delay in reviewing. Pushed an update just to trigger the actions again.

@etep Could you give an approval if you think this is good to go @benkilimnik If you've done additional testing to ensure that this works (eg. on kernels older than...

> @JamesMBartlett `std::unique_ptr` runs into problems since [this](https://github.com/pixie-io/pixie/blob/79886a48cd2f8a1b77a57b2a314dfe708454f8ce/src/stirling/bpf_tools/bcc_wrapper.cc#L190) relies on a copy constructor being present. Instead of trying to working around that, I chose to use a `std::shared_ptr`. Let me...

> In order to test this out, I have a very crude experiment that updates the vizier SANs to use the cluster domain rather than the hardcoded `cluster.local` and have...

I assume by "functions" you're talking about calling existing PxL scripts, like `px/perf_flamegraph` rather than actual functions within a PxL script. Is that correct?

Hi there! Could you please list the steps you followed to reproduce this issue? Also in the future, please follow our bug report issue template.

Hi @dcfranca. It's hard for us to debug issues in environments we don't officially support. I'm not too familiar with Colima. However, it seems like they have an option to...

The version of Elasticsearch in the stackoverflow you linked is 7.10.2. Pixie currently uses 7.6. It's possible this is an issue with elasticsearch that got fixed between 7.6 and 7.10.2....