Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[refactor] [server] Refactor ByteBuf release method in module distributedlog-core/distributedlog-protocol #3693

Conversation

StevenLuMT
Copy link
Member

Motivation

It may throw an exception when release a ByteBuf object. so the exception in ByteBuf.release should be checked.

Changes

  1. Use ReferenceCountUtil.safeRelease() instead of ByteBuf.release() in module distributedlog-core/distributedlog-protocol

@StevenLuMT StevenLuMT requested a review from zymap December 6, 2022 10:14
@hangc0276
Copy link
Contributor

@StevenLuMT Please do not tag cherry-picked/xx on Prs, which is not cherry-picked to the target branch.

@StevenLuMT
Copy link
Member Author

@StevenLuMT Please do not tag cherry-picked/xx on Prs, which is not cherry-picked to the target branch.

Got it ,thanks @hangc0276

@StevenLuMT StevenLuMT merged commit a71c7a7 into apache:master Dec 7, 2022
hangc0276 pushed a commit that referenced this pull request Dec 8, 2022
…f release usage (#3693)

Co-authored-by: lushiji <[email protected]>
(cherry picked from commit a71c7a7)
nicoloboschi pushed a commit to datastax/bookkeeper that referenced this pull request Jan 11, 2023
…f release usage (apache#3693)

Co-authored-by: lushiji <[email protected]>
(cherry picked from commit a71c7a7)
(cherry picked from commit 8e352d4)
yaalsn pushed a commit to yaalsn/bookkeeper that referenced this pull request Jan 30, 2023
@hangc0276 hangc0276 added this to the 4.16.0 milestone Mar 21, 2023
Ghatage pushed a commit to sijie/bookkeeper that referenced this pull request Jul 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants