Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

idle timeout test failure from upstream change #2108

Closed
snowp opened this issue Mar 16, 2022 · 0 comments · Fixed by #2658
Closed

idle timeout test failure from upstream change #2108

snowp opened this issue Mar 16, 2022 · 0 comments · Fixed by #2658

Comments

@snowp
Copy link
Contributor

snowp commented Mar 16, 2022

Brining envoyproxy/envoy@d7edf3b in results in some issues (see #2105)

To unblock upgrading we're disabling this change via runtime, but we'll need to figure out the cause of the disruption sometime before the runtime guard is removed

alyssawilk pushed a commit that referenced this issue Nov 3, 2022
Description: Remove the use of removed override_request_timeout_by_gateway_timeout upstream Envoy flag from Swift tests. The flag was removed from the main config.cc as part of #2296 file months ago. The original removal introduced a bug as filter's onError callback started being called twice - this PR fixes this issue. Update EM code to correctly handle stream idle. See #2639 for more details. Fixes #2108.
Risk Level: Medium, touches stream onDestroy code.
Testing: Unit/Integration tests.
Docs Changes: N/A
Release Notes: N/A

Signed-off-by: Rafal Augustyniak <raugustyniak@lyft.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant