async_tcp_client: remove callbacks if connection was not closed#35410
Merged
ggreenway merged 8 commits intoenvoyproxy:mainfrom Aug 1, 2024
Merged
async_tcp_client: remove callbacks if connection was not closed#35410ggreenway merged 8 commits intoenvoyproxy:mainfrom
ggreenway merged 8 commits intoenvoyproxy:mainfrom
Conversation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Commit Message: when the
AsyncTcpClientis being destroyed but it also has an active client connection, there's a crash since during the instance destruction, theClientConnectionobject would also be destroyed, causingraiseEventto be called back toAsyncTcpClientwhile it is being destroyedAdditional Description: Caught with the following stack trace:
Risk Level: low
Testing: unit tests
Docs Changes: none
Release Notes: none
Platform Specific Features: none