refactor(init): replace fixed delay with event-driven block processing readiness#8948
Merged
AnkushinDaniil merged 2 commits intoJul 8, 2025
Merged
Conversation
…g readiness - Add ProcessingCompletedTask to IBlockProcessingQueue for async readiness signaling - Implement TaskCompletionSource-based readiness in BlockchainProcessor - Refactor RegisterPluginRpcModules to await true block processing completion - Remove all arbitrary delays and polling from plugin RPC module initialization - Ensures RPC modules are only enabled after all blocks are processed, eliminating race conditions and startup lag
wurdum
requested changes
Jul 7, 2025
wurdum
approved these changes
Jul 7, 2025
3e549ad
into
feature/arbitrum-setup
178 of 182 checks passed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Fixes Closes Resolves #63
Please choose one of the keywords above to refer to the issue this PR solves followed by the issue number (e.g. Fixes #000). If no issue number, remove the line. Also, remove everything marked optional that is not applicable. Remove this note after reading.
Changes
Types of changes
What types of changes does your code introduce?
Testing
Requires testing
If yes, did you write tests?
Notes on testing
Optional. Remove if not applicable.
Documentation
Requires documentation update
If yes, link the PR to the docs update or the issue with the details labeled
docs. Remove if not applicable.Requires explanation in Release Notes
If yes, fill in the details here. Remove if not applicable.
Remarks
Optional. Remove if not applicable.