[Branch-2.9][fix][client] Fix MaxQueueSize semaphore release leak in createOpSendMsg. #16958
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
Nicklee007
changed the title
1 task
Jason918
approved these changes
Aug 7, 2022
codelipenghui
added
release/2.9.4
cherry-picked/branch-2.9
|
@Nicklee007 Please help resolve the conflicts |
Nicklee007
force-pushed
the
chrry-pick-PR16915-PR16837-to-branch-2.9
branch
from
1ec9e3d
to
2fd6ac9
Compare
Nicklee007
force-pushed
the
chrry-pick-PR16915-PR16837-to-branch-2.9
branch
from
2fd6ac9
to
4c9a410
Compare
@codelipenghui resolved, PTAL |
Technoboy-
approved these changes
Aug 9, 2022
|
@Nicklee007 Very thanks to you. |
2 tasks
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.
Motivation
This PR is part of work of cherry-pick #16915 to branch 2.9
Release MaxQueueSize semaphore when invalid message.
Modifications
Documentation
doc-not-needed(Please explain why)