fix: clean up persisted accounts after owned mode changes - #167
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 (1)
Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe persisted check now accepts owned accounts when their mode is authoritative or their mode marker is dirty. This lets mode-transition entries reach persisted cleanup. Borrowed-account handling is unchanged. Priority: ➖ Normal Change: Bug fix · Severity of issue fixed: Medium Merge Risk: ⚪ Minimal · up to The change makes resolving a Transient account to ReadOnly remove its persisted copy even when the image is promoted to owned storage. No concrete merge-blocking risk was identified in the reviewed change. 🚥 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
Resolving a Transient account to ReadOnly now removes its persisted copy even when data growth promotes the borrowed image to owned storage. Owned accounts with a dirty mode marker reach the existing persisted cleanup path, preventing duplicate program-scan entries and stale state resurfacing after volatile eviction.
Closes #166
Impact
Ordinary ReadOnly refreshes still avoid persisted writes. This prevents new stale copies; it does not repair copies left behind before the fix.