-
Notifications
You must be signed in to change notification settings - Fork 1.2k
chore: drop legacy CDeterministicMNState
formats, evodb upgrade logic
#6579
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
Conversation
Co-authored-by: UdjinM6 <[email protected]>
WalkthroughThe pull request removes legacy support for migrating EvoDb databases and handling outdated formats within the deterministic masternode management code. The documentation has been updated to advise users upgrading from versions 19 and 20 to reindex their databases. In the code, functions and logic related to migrating or reading from older EvoDB formats have been eliminated. Specifically, migration methods in the deterministic masternode manager and compatibility constructors for legacy masternode states were removed, as well as constants and enumeration values related to older formats and upgrade errors. Modifications in the chainstate loading process also remove specific calls and error handling for EvoDb migrations, thereby streamlining the overall initialization, serialization, and state management processes. Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
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.
Actionable comments posted: 0
🧹 Nitpick comments (1)
src/evo/deterministicmns.h (1)
76-79
: Consider providing more user guidance in the exception message.
Although throwing an exception is correct for dropping older formats, you might include additional steps or references within this message (e.g., pointing users to release notes) to help them troubleshoot reindex requirements more easily.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (7)
doc/release-notes-6579.md
(1 hunks)src/evo/deterministicmns.cpp
(0 hunks)src/evo/deterministicmns.h
(2 hunks)src/evo/dmnstate.h
(0 hunks)src/init.cpp
(0 hunks)src/node/chainstate.cpp
(0 hunks)src/node/chainstate.h
(0 hunks)
💤 Files with no reviewable changes (5)
- src/node/chainstate.cpp
- src/node/chainstate.h
- src/evo/deterministicmns.cpp
- src/evo/dmnstate.h
- src/init.cpp
✅ Files skipped from review due to trivial changes (1)
- doc/release-notes-6579.md
🔇 Additional comments (3)
src/evo/deterministicmns.h (3)
84-84
: No further concerns on thepdmnState
field.
READWRITE forpdmnState
is consistent with dropping old states and uses the updated format logic correctly.
88-88
: Good approach for handling type properly based on version.
The version check ensures backward compatibility for older network peers by defaulting toMnType::Regular
.
214-214
: Logic looks good for deserializing and adding masternodes.
Creation ofCDeterministicMN
instances using the new format version is aligned with the removal of old formats.
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.
utACK 39f76c8
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.
utACK 39f76c8
…Werror` for Clang, merge bitcoin#13633 c7748cd revert: don't build using `-Werror` when using Clang (Kittywhiskers Van Gogh) 1015f9b fix: resolve `-Wunreachable-code` warnings, add comment for explanation (Kittywhiskers Van Gogh) 10cb3e4 fix: resolve `-Wlogical-op-parentheses` warnings (Kittywhiskers Van Gogh) 7459b1e fix: resolve `-Wunused-private-field` warnings (Kittywhiskers Van Gogh) 7a52083 fix: resolve `-Wmissing-field-initializers` warnings (Kittywhiskers Van Gogh) 184b463 fix: resolve `-Wdelete-non-abstract-non-virtual-dtor` warnings (Kittywhiskers Van Gogh) 53d29e9 fix: sidestep `-Wunused-function` warnings with `[[maybe_unused]]` (Kittywhiskers Van Gogh) 9315e69 move-only: keep functions used in wallet-enabled segments within macro (Kittywhiskers Van Gogh) 6729d69 fix: add missing lock annotation in lambda expression (Kittywhiskers Van Gogh) f6d1eb9 chore: drop extraneous unused `ApplyStats()` definition (Kittywhiskers Van Gogh) df9c926 chore: drop unused `EraseOldDBData()` (Kittywhiskers Van Gogh) c9cb9a6 merge bitcoin#13633: Drop dead code from Stacks (Kittywhiskers Van Gogh) Pull request description: ## Additional Information * Depends on #6637 * Dependency for #6639 * While [bitcoin#13633](bitcoin#13633) was originally marked as DNM in the backports spreadsheet for being SegWit-related, it's not SegWit-_dependent_ and is for dead code removal, which is necessary due to the enforcement of `-Wunused-function`. It has therefore been included. * `EraseOldDBData()` fell into disuse after [dash#6579](#6579) but wasn't removed then. It has been removed now due to `-Wunused-function` enforcement. * An extraneous `ApplyStats()` definition was left over when backporting [bitcoin#19145](bitcoin#19145). It has been removed now due to `-Wunused-function` enforcement. * [bitcoin#25337](bitcoin#25337) ([commit](a7d4127)) did not include a lock annotation for the lambda expression in `ListReceived()`. It has been added alongside `AssertLockHeld`s for both the lambda expression and the function. This was done to pass `-Wthread-safety` enforcement. * `ParsePubKeyIDFromAddress()`, `ParseBLSPubKey()` and `ValidatePlatformPort()` have been moved inside the `ENABLE_WALLET` macro conditional to avoid `-Wunused-function` warnings if building with wallets disabled. * Some dead code cannot be removed because they are either part of partial backports that may be completed in the future or complicate backports in the future that may expect their presence. To keep `-Wunused-function` happy, they have been marked with `[[maybe_unused]]` and this annotation should be removed when they are used. ## Breaking Changes None expected. ## Checklist - [x] I have performed a self-review of my own code - [x] I have commented my code, particularly in hard-to-understand areas - [x] I have added or updated relevant unit/integration/functional/e2e tests **(note: N/A)** - [x] I have made corresponding changes to the documentation **(note: N/A)** - [x] I have assigned this pull request to a milestone _(for repository code-owners and collaborators only)_ ACKs for top commit: UdjinM6: utACK c7748cd PastaPastaPasta: utACK c7748cd Tree-SHA512: 5d746773a1f49c33f373250ba459a5da4301fea0cb5202d26717808d8a4985920cbdfec0903ed884f20561f8d40082b4ea796e78912bacff00e0645d355ec9f2
Additional Information
CDeterministicMNState_
{Oldformat
,mntype_format
} was introduced in dash#5039 and dash#5403, included in Dash Core v19 and v20 respectively.The above change has been in the codebase for more than two major releases and does not concern databases with a long shelf life (like wallets), this pull request removes them entirely.
Breaking Changes
Users upgrading from these versions are now expected to
-reindex
.Checklist: