fix(*): avoid infinite loop when notifications close #398
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lsytj0413
requested review from
merlimat,
mattisonchao,
coderzc and
RobertIndie
as code owners
lsytj0413
force-pushed
the
fix-notification-close
branch
from
a66cdc9 to
69b0970
Compare
Signed-off-by: Soren Yang <[email protected]>
lsytj0413
force-pushed
the
fix-notification-close
branch
from
69b0970 to
77780ea
Compare
merlimat
approved these changes
Dec 6, 2023
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.
The original for loop never change the initialize
n, it will cause infinite loop when channel is not empty when close started.