eric846
eric846
One "third-party tunnel" you might consider is an Envoy proxy running on your machine between Nighthawk and the password-protected proxy. See https://github.com/envoyproxy/envoy/issues/11308
A couple of things to watch out for: - The HTTP tunnel might end up being the bottleneck -- may need to keep an eye on it and possibly tune...
With this customization removed, ASAN tests failed repeatedly on 2023-09-10: https://github.com/envoyproxy/nighthawk/pull/1022.
Sorry about that. The -lrt -latomic was needed for the CI build to work after updating to the latest Envoy. But these flags were actually not needed to build on...
Meanwhile if it's possible to edit the docker file locally before you run it, you might be able to fix it with: apk add libatomic
I see what you mean about the tags on docker hub. The most recent tag is 3 years old. Unfortunately I tried the `apk add libatomic` workaround locally and it...
That is a great idea, and it appears to work. Created https://github.com/envoyproxy/nighthawk/pull/1314
Thank you @zirain for validating Ubuntu. https://github.com/envoyproxy/nighthawk/pull/1315 will migrate the image to Ubuntu.
The new image is live. Let us know if it works! ``` docker rmi envoyproxy/nighthawk-dev:latest docker run envoyproxy/nighthawk-dev:latest nighthawk_client ```
> So the tsan test failed on "//test:service_test" I can't surface the details yet from https://mordenite.cluster.engflow.com/invocations/default/fbf47dbf-216e-41c4-8610-49961bb61e89#console > > It looks like either a process is hanging, or details are still...