jsonrpc: don't explicitly remove old tables #19944
Merged
+9
−14
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
bmwill
requested review from
johnjmartin,
ebmifa,
phoenix-o,
sadhansood and
pei-mysten
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
3 Skipped Deployments
|
phoenix-o
approved these changes
Oct 21, 2024
Don't explicitly remove old jsonrpc index tables as well as remove a possible panic when reporting rocksdb metrics.
bmwill
force-pushed
the
jsonrpc-index-remove-table-fix
branch
from
c286854 to
9e7d7eb
Compare
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.
Don't explicitly remove old jsonrpc index tables as well as remove a possible panic when reporting rocksdb metrics.
Description
Describe the changes or additions included in this PR.
Test plan
How did you test the new or updated feature?
Release notes
Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required.
For each box you select, include information after the relevant heading that describes the impact of your changes that a user might notice and any actions they must take to implement updates.