Dom Delnano

Thanks for providing that context. I was able to debug my problem and while the error message matched what was reported here, my issue was self inflicted and is resolved.

@kpattaswamy any concerns with merging this change (assuming the build passes)? I don't remember exactly what wire protocol version of Mongodb we support, but this client upgrade doesn't seem to...

@hengyoush thanks for the detailed bug report. There are some well known issues that cause missing protocol traces as payload size increases (https://github.com/pixie-io/pixie/issues/1755 for example). I need to spend some...

@ashutoshrathore gave this a try once #1887 was merged. While this fixed the issues with the DaemonSet pods, the expected behaviors was to be able to control the scheduling of...

@flyme001 please confirm that your k8s cluster is able to pull those images. It seems like your cluster might be firewalled off from gcr.io.

@maxlemieux this will be fixed in the next Pixie release v0.14.10 and should be available sometime early this week. This issue was addressed in #1909.

v0.14.10 is released.

Hi @hkraal, thanks for being active in providing feedback. Unfortunately, I think there are some potentially large breaking changes that could come (#211 being one that will likely be disruptive,...

Access over http seems to work 👍 ``` vagrant@vagrant:/code/netty-tcnative$ curl localhost:8099/maven Repository Mappings ------------------- central --> https://repo.maven.apache.org/maven2 releases --> https://www.releases-repo.com/ snapshots --> https://repo.maven.apache.org/maven2 ``` I assume there should be a...

I'm no longer at New Relic and won't be able to ensure this change gets merged. So another maintainer will have to help this change get through.