fix: record committed balances for failed transactions - #165
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. 📝 WalkthroughWalkthroughWhen execution fails, Priority: ➖ Normal Change: Bug fix · Severity of issue fixed: Low Merge Risk: ⚪ Minimal · up to Failed transaction receipts now report balances consistent with rolled-back account state. No concrete merge-blocking issue remains; the change is mergeable after normal checks. 🚥 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
Failed transactions no longer record lamport moves from earlier successful instructions in their
postBalances. Keeper now records the pre-execution balances as post balances when execution fails, matching the account state Engine commits. Fees are currently zero on the ER.Closes #164