build: Moving more downstream code into the listener extension#24495
build: Moving more downstream code into the listener extension#24495alyssawilk merged 3 commits intoenvoyproxy:mainfrom
Conversation
Signed-off-by: Alyssa Wilk <alyssar@chromium.org>
Signed-off-by: Alyssa Wilk <alyssar@chromium.org>
Signed-off-by: Alyssa Wilk <alyssar@chromium.org>
| if (factory) { | ||
| return factory->createConnectionHandler(dispatcher, absl::nullopt); | ||
| } | ||
| ENVOY_LOG_MISC(debug, "Unable to find envoy.connection_handler.default factory"); |
There was a problem hiding this comment.
There should be an assertion? since it should never happen? as I understand, we won't make this configurable.
There was a problem hiding this comment.
this should never happen in upstream Envoy. it can in Envoy mobile if you misconfigure things.
There was a problem hiding this comment.
Would that be due to failing to register the factory? Or is there some config that drives this?
In general EM does crash on missing registration, though I guess just logging might be better?
There was a problem hiding this comment.
This is hit in Envoy Mobile which makes mobile application crash after we call addDirectResponse on TestEngineBuilder (as it adds a listener) (iOS only API). Not sure whether it crashes in any other cases but in general this method always returns nullptr.
| return factory->createConnectionHandler(dispatcher, index); | ||
| } | ||
| ENVOY_LOG_MISC(debug, "Unable to find envoy.connection_handler.default factory"); | ||
| return nullptr; |
envoyproxy#24495)" This reverts commit d78e0c8.
Risk Level: low Testing: n/a Docs Changes: n/a Release Notes: n/a part of envoyproxy/envoy-mobile#2711 #24495 now with merge fix Signed-off-by: Alyssa Wilk <alyssar@chromium.org>
Commit Message: A follow up fixes to #24495. Without these fixes application crashes after `addDirectResponse` call on `TestEngineBuilder` (iOS only api) as the `handler_` in https://github.com/envoyproxy/envoy/blob/93ea91f42ef749a4560a4596174402a5aad8ee65/source/server/worker_impl.cc#L61 is `nullptr`. Additional Description: The question is whether without the added registration calls application may crash even without the `addDirectResponse` call. cc @alyssawilk. Asking since Lyft has pushed #24495 to prod pipeline already and the question is whether we need to cherry-pick the fix from this PR now. Risk Level: Low Testing: Docs Changes: Release Notes: Platform Specific Features: [Optional Runtime guard:] [Optional Fixes #Issue] [Optional Fixes commit #PR or SHA] [Optional Deprecated:] [Optional [API Considerations](https://github.com/envoyproxy/envoy/blob/main/api/review_checklist.md):] Signed-off-by: Rafal Augustyniak <raugustyniak@lyft.com>
…roxy#24495 Risk Level: low Testing: n/a Docs Changes: n/a Release Notes: n/a part of envoyproxy/envoy-mobile#2711 envoyproxy#24495 now with merge fix Signed-off-by: Alyssa Wilk <alyssar@chromium.org> Signed-off-by: Ohad Vano <ohadvano@microsoft.com>
Commit Message: A follow up fixes to envoyproxy#24495. Without these fixes application crashes after `addDirectResponse` call on `TestEngineBuilder` (iOS only api) as the `handler_` in https://github.com/envoyproxy/envoy/blob/93ea91f42ef749a4560a4596174402a5aad8ee65/source/server/worker_impl.cc#L61 is `nullptr`. Additional Description: The question is whether without the added registration calls application may crash even without the `addDirectResponse` call. cc @alyssawilk. Asking since Lyft has pushed envoyproxy#24495 to prod pipeline already and the question is whether we need to cherry-pick the fix from this PR now. Risk Level: Low Testing: Docs Changes: Release Notes: Platform Specific Features: [Optional Runtime guard:] [Optional Fixes #Issue] [Optional Fixes commit #PR or SHA] [Optional Deprecated:] [Optional [API Considerations](https://github.com/envoyproxy/envoy/blob/main/api/review_checklist.md):] Signed-off-by: Rafal Augustyniak <raugustyniak@lyft.com> Signed-off-by: Ohad Vano <ohadvano@microsoft.com>
…roxy#24495 Risk Level: low Testing: n/a Docs Changes: n/a Release Notes: n/a part of envoyproxy/envoy-mobile#2711 envoyproxy#24495 now with merge fix Signed-off-by: Alyssa Wilk <alyssar@chromium.org> Signed-off-by: VishalDamgude <vishal.damgude@freshworks.com>
Commit Message: A follow up fixes to envoyproxy#24495. Without these fixes application crashes after `addDirectResponse` call on `TestEngineBuilder` (iOS only api) as the `handler_` in https://github.com/envoyproxy/envoy/blob/93ea91f42ef749a4560a4596174402a5aad8ee65/source/server/worker_impl.cc#L61 is `nullptr`. Additional Description: The question is whether without the added registration calls application may crash even without the `addDirectResponse` call. cc @alyssawilk. Asking since Lyft has pushed envoyproxy#24495 to prod pipeline already and the question is whether we need to cherry-pick the fix from this PR now. Risk Level: Low Testing: Docs Changes: Release Notes: Platform Specific Features: [Optional Runtime guard:] [Optional Fixes #Issue] [Optional Fixes commit #PR or SHA] [Optional Deprecated:] [Optional [API Considerations](https://github.com/envoyproxy/envoy/blob/main/api/review_checklist.md):] Signed-off-by: Rafal Augustyniak <raugustyniak@lyft.com> Signed-off-by: VishalDamgude <vishal.damgude@freshworks.com>
Risk Level: low
Testing: n/a
Docs Changes: n/a
Release Notes: n/a
part of envoyproxy/envoy-mobile#2711