fix: restore processed signatures on restart - #98
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (14)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe ledger now returns indexed transaction signatures and terminal statuses in block history. Keeper startup builds a unified cache seed from retained history and 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Full details: Linked Issues checkExplanation The changes satisfy issue Full details: Docstring CoverageExplanation Docstring coverage is 94.59% which is sufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 37 functions across 10 files. (4 skipped: 4 unsupported.) ✨ 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
Closes #97
Impact
Previously processed transactions remain deduplicated across clean restarts and snapshot-tail recovery.
BlockRangePayloadhas a breaking in-process response type; the on-disk ledger format is unchanged.Reviewer notes
Startup history is bounded by the largest cache or
SlotHasheswindow and inserted oldest-to-newest at original block slots. Replay updates the signature cache only after re-execution advances state and deliberately bypasses live ledger and subscription fanout.