Repository navigation
refactor(dash-spv): clean up the masternode engine storage - #1246
Conversation
The client truncated the engine after `StorageManager::truncate_above`, which truncated the same shared engine again. Storage now runs the engine step even when the chain steps fail, and the client no longer repeats it.
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 45 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Waiting for bot review — coderabbitai not yet. Wait for the missing reviews, or a writer can post |
|
Waiting for bot review — coderabbitai not yet. Wait for the missing reviews, or a writer can post |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## dev #1246 +/- ##
==========================================
- Coverage 79.06% 79.05% -0.02%
==========================================
Files 298 298
Lines 79058 79057 -1
==========================================
- Hits 62506 62495 -11
- Misses 16552 16562 +10
|
|
/skip-bots |
|
/self-reviewed |
|
Policy satisfied — this can merge. |
Split out of #1227. Three small cleanups in the masternode storage, independent of the snapshot codec:
headersfield ofPersistentMasternodeStorage.StorageManager::truncate_above, which truncated the same shared engine again. Storage now runs the engine step even when the chain steps fail, and the client no longer repeats it.get_quorum_at_heightresolves.PR Hygiene ·
122c133When every merge requirement is met, the
PR Hygienecheck passes. Reviewer limits do not block merging; other required GitHub checks and protections still apply.