envoy: update submodule 46b646c -> 33cf6cd#1481
Conversation
Signed-off-by: Ryan Northey <ryan@synca.io>
|
not sure if failing tests are flakes - im struggling to get any info when clicking on the "details" link |
|
The python one might be a flake that @crockeo was looking into but the core test likely is unexpected. I just reran both the jobs and am hoping that makes it green |
|
@buildbreaker checking the swift_helloworld test it seems to be failing with: this was the reason that i added in the xff extension in the build config. its not clear to me why this is still failing, where the config is coming from, or why the envoy binary doesnt have the extension added im guessing that the problem is related to the ip detection extension being listed as required in envoy's any ideas ? |
|
@phlax sorry I didn't see this sooner - if you're adding an extension, it will need to be registered here: |
|
This has to do with differences in static initialization order when running as a process vs. running as a statically-linked library. |
|
great, thanks - ill update shortly |
Signed-off-by: Ryan Northey <ryan@synca.io>
Signed-off-by: Ryan Northey <ryan@synca.io>
|
@goaway ive tried registering the extension - unfortunately it causes an error - something to do with namespacing and factories im afraid this is about my limit of c++ knowledge - if you can lmk what else is required i would be happy to add |
Signed-off-by: Mike Schore <mike.schore@gmail.com>
Signed-off-by: Mike Schore <mike.schore@gmail.com>
Signed-off-by: Mike Schore <mike.schore@gmail.com>
Signed-off-by: Ryan Northey ryan@synca.io
Description:
When testing #1475 tests were failing as the envoy submodule was behind envoy main
This PR also:
envoy.http.original_ip_detection.xffextension as tests seemed to indicate it as necessaryRisk Level:
Testing:
Docs Changes:
Release Notes:
[Optional Fixes #Issue]
[Optional Deprecated:]