fix(comms): ensure that inbound messaging terminates on disconnect #6653
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.
Description
fix(comms): ensure that inbound messaging terminates on disconnect
Motivation and Context
Ensure that the inbound messaging worker terminates when the peer connection is disconnected.
This PR ensures this by using the
PeerConnection::on_disconnect
future. It has not been confirmedthat the inbound worker would not terminate before however this PR will guarantee it.
How Has This Been Tested?
Updated unit tests.
What process can a PR reviewer use to test or verify this change?
Breaking Changes