Evo: Preserve DMN history across reorgs - #1932
Conversation
🤖 CodeAnt AI — Review Status
|
Thanks for using CodeAnt! 🎉We're free for open-source projects. if you're enjoying it, help us grow by sharing. Share on X · |
|
Warning Review limit reachedNext included review available in 59 minutes. View limit detailsLimit details: You’ve used all 4 included reviews currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
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 |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
User descriptionPreserve persisted deterministic-masternode diffs and snapshots when disconnecting blocks, while evicting only the in-memory cache entry. Add a regression test proving orphan history remains reconstructible across reorgs. CodeAnt-AI DescriptionPreserve deterministic masternode history after chain reorganizations What Changed
Impact
💡 Usage GuideChecking Your Pull RequestEvery time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later. Talking to CodeAnt AIGot a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask: This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code. ExamplePreserve Org Learnings with CodeAntYou can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input: This helps CodeAnt AI learn and adapt to your team's coding style and standards. ExampleRetrigger reviewAsk CodeAnt AI to review the PR again, by typing: Check Your Repository HealthTo analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health. |
CodeAnt Nitpicks1 code suggestion1. The test checks only MN membership and metadata, so incorrect collateral, registration, confirmation, or PoSe state can be restored without failing.Incomplete implementation · |
reubenyap
left a comment
There was a problem hiding this comment.
Reviewed the current head and traced disconnects through the EvoDB transaction, cache eviction, list reconstruction, reconnect, and VerifyDB rollback paths. Keeping the persisted diff/snapshot while evicting the disconnected block from memory preserves orphan history without letting stale cached state drive the active tip. The regression and full CI matrix are green. I found no actionable issues.
Preserve persisted deterministic-masternode diffs and snapshots when disconnecting blocks, while evicting only the in-memory cache entry. Add a regression test proving orphan history remains reconstructible across reorgs.
Upstream: Dash PR #3435.