fix(mempool)!: Remove VM keeper end blocker notification, use PrepareCheckStater instead#1146
Conversation
Greptile SummaryThis PR removes the incorrect Confidence Score: 5/5Safe to merge — all previously flagged issues are resolved and no new P0/P1 issues found The three issues from previous review rounds (P0 compile error, stale doc comment, dead struct field) are all cleanly fixed. The new PrepareCheckStater hook fires at the correct lifecycle point, the NotifyNewBlock() refactor preserves both the blockchain notification and cosmos pool recheck in both paths, and all interface/mock/import cleanup is consistent. No files require special attention Important Files Changed
|
… does not have an event bus configured
f47d9f4 to
ba1429f
Compare
|
@greptile re review pls |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1146 +/- ##
==========================================
+ Coverage 65.27% 66.20% +0.93%
==========================================
Files 336 336
Lines 23903 23844 -59
==========================================
+ Hits 15602 15787 +185
+ Misses 6937 6885 -52
+ Partials 1364 1172 -192
🚀 New features to boost your workflow:
|
Description
Removes the ability to notify the mempool of new blocks within the vm keepers end blocker. This is strictly incorrect now since it will trigger a reset of the mempool on stale state. This behavior is replicated by using the
PrepareCheckStaterhook that is called just after a block is committed and the check state is updated.Closes: STACK-2688
Author Checklist
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...
mainbranch