Move FinalizeBlock event staging logic into a generic EventStager (backport #2435) #2436
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changelist
Create a new
EventStager
struct that manages the staging and retrieval ofFinalizeBlock
event, so that it can be used by all modules.Test Plan
Tested FNS via localnet.
Author/Reviewer Checklist
state-breaking
label.indexer-postgres-breaking
label.PrepareProposal
orProcessProposal
, manually add the labelproposal-breaking
.feature:[feature-name]
.backport/[branch-name]
.refactor
,chore
,bug
.Summary by CodeRabbit
New Features
EventStager
for efficient staging and retrieval of events during the FinalizeBlock process.FullNodeStreamingManager
with a new dependency on thefinalizeblock
package.Bug Fixes
Documentation
SendFinalizedSubaccountUpdates
method across various components.This is an automatic backport of pull request #2435 done by [Mergify](https://mergify.com).