This repository has been archived by the owner on Nov 15, 2023. It is now read-only.
Drain all the pending messages in the channel when TracingUnboundedReceiver
is dropped
#13917
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.
Fix #13849
tracing_unbounded
usesasync_channel
internally, in which, the pending messages of the channel will not be dropped even if all the receivers have been dropped and these messages can never be accessed.This may cause blocking issues when using
tracing_unbounded
to sendSender<T>
and there is quite a lot of such usage within substrate as #13849 mentioned.This PR fixes the issue by manually draining all the pending messages in the channel when
TracingUnboundedReceiver
is dropped and a test is added to cover the abovementioned case.cc @bkchr