fix: remove orphaned snapshot exports at startup - #158
Conversation
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository: magicblock-labs/magicblock-engine/.coderabbit.yaml Review profile: ASSERTIVE Plan: Advanced Run ID: 📒 Files selected for processing (3)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthrough
Fixed issue severity: <fixed_issue_severity>Medium</fixed_issue_severity> Priority: ➖ Normal Change: Bug fix Merge Risk: ⚪ Minimal · up to The startup cleanup appears ready to merge after normal checks; no supported path was found that would prevent it from removing orphaned exports. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
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 |
What changed
An interrupted seal can leave a temporary AccountsDB export directory behind. Keeper now removes orphaned exports at startup, before archival begins, so a later seal can reuse the path.
Closes #157
Related: magicblock-labs/magicblock-validator#1731
Impact
Startup treats every
snapshot-*entry under the AccountsDB root as an owned temporary export. Retained snapshots in the ledger are unaffected.