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

check plugin name on plugin_reload rpc call #33582

Merged
merged 2 commits into from
Nov 1, 2023

Conversation

fanatid
Copy link
Contributor

@fanatid fanatid commented Oct 7, 2023

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.

@mergify mergify bot added community Community contribution need:merge-assist labels Oct 7, 2023
@mergify mergify bot requested a review from a team October 7, 2023 18:41
@github-actions github-actions bot added the stale [bot only] Added to stale content; results in auto-close after a week. label Oct 23, 2023
@github-actions github-actions bot closed this Oct 31, 2023
@fanatid
Copy link
Contributor Author

fanatid commented Oct 31, 2023

@lijunwangs can you check this, please?

Copy link

codecov bot commented Oct 31, 2023

Codecov Report

Merging #33582 (2687f41) into master (c588f25) will increase coverage by 0.0%.
Report is 192 commits behind head on master.
The diff coverage is 28.5%.

@@           Coverage Diff           @@
##           master   #33582   +/-   ##
=======================================
  Coverage    81.7%    81.7%           
=======================================
  Files         807      807           
  Lines      218283   218290    +7     
=======================================
+ Hits       178485   178491    +6     
- Misses      39798    39799    +1     

@github-actions github-actions bot removed the stale [bot only] Added to stale content; results in auto-close after a week. label Nov 1, 2023
Copy link
Contributor

@lijunwangs lijunwangs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good

@lijunwangs lijunwangs added the CI Pull Request is ready to enter CI label Nov 1, 2023
@solana-grimes solana-grimes removed the CI Pull Request is ready to enter CI label Nov 1, 2023
@lijunwangs lijunwangs merged commit 808f67a into solana-labs:master Nov 1, 2023
19 checks passed
@fanatid fanatid deleted the rpc-geyser-reload-plugin branch November 2, 2023 10:16
@lijunwangs lijunwangs added the v1.17 PRs that should be backported to v1.17 label Jan 5, 2024
Copy link
Contributor

mergify bot commented Jan 5, 2024

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.

mergify bot pushed a commit that referenced this pull request Jan 5, 2024
* check plugin name on plugin_reload rpc call

* add name to error message

(cherry picked from commit 808f67a)
lijunwangs pushed a commit that referenced this pull request Jan 10, 2024
… (#34668)

check plugin name on plugin_reload rpc call
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community Community contribution need:merge-assist v1.17 PRs that should be backported to v1.17
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants