-
Notifications
You must be signed in to change notification settings - Fork 5.1k
GeyserPluginService: Use common exit
flag.
#31915
Conversation
Geyser plugin thread would never shutdown correctly, as it is using an exit flag that is never set.
Codecov Report
@@ Coverage Diff @@
## master #31915 +/- ##
=========================================
- Coverage 81.9% 81.9% -0.1%
=========================================
Files 757 757
Lines 207054 207053 -1
=========================================
- Hits 169648 169645 -3
- Misses 37406 37408 +2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just to save someone else the verification I just did, #30352 added an earlier exit
on L492. I was concerned the duplication was deliberate as part of hot-reloading geyser plugins. However, that PR also removed this later exit
. This line was re-added in #30645 in what I believe was a bad rebase (touches adjacent code, merged one day later).
Anyway, thank you for fixing this @ilya-bobyr. I think we should backport to v1.16
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, good find!
And thanks for tracking down the specific PR's @CriesofCarrots, agreed with your assessment as to why we had two exit
s. And agreed on backporting.
Thank you for checking! |
Thinking a bit more about this. |
Problem
Geyser plugin thread would never shutdown correctly, as it is using an exit flag that is never set.
Summary of Changes
Use common exit flag.
And a minor refactoring in the
use
statement.