-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
check plugin name on plugin_reload rpc call #33582
check plugin name on plugin_reload rpc call #33582
Conversation
@lijunwangs can you check this, please? |
Codecov Report
@@ Coverage Diff @@
## master #33582 +/- ##
=======================================
Coverage 81.7% 81.7%
=======================================
Files 807 807
Lines 218283 218290 +7
=======================================
+ Hits 178485 178491 +6
- Misses 39798 39799 +1 |
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.
looks good
Backports to the beta branch are to be avoided unless absolutely necessary for fixing bugs, security issues, and perf regressions. Changes intended for backport should be structured such that a minimum effective diff can be committed separately from any refactoring, plumbing, cleanup, etc that are not strictly necessary to achieve the goal. Any of the latter should go only into master and ride the normal stabilization schedule. Exceptions include CI/metrics changes, CLI improvements and documentation updates on a case by case basis. |
* check plugin name on plugin_reload rpc call * add name to error message (cherry picked from commit 808f67a)
… (#34668) check plugin name on plugin_reload rpc call
Problem
On
plugin_reload
we need to check the new plugin name, the path to the plugin can be changed in the config file, and as a result, already loaded plugin can be loaded again.Summary of Changes
Add plugin name check.