Support lazy-initialization for all services #1454
Merged
Conversation
This file contains 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
goshawk-3
force-pushed
the
init_services
branch
from
f591441 to
0d9fce1
Compare
goshawk-3
force-pushed
the
init_services
branch
from
5b8f734 to
359fa55
Compare
herr-seppia
approved these changes
Feb 27, 2024
herr-seppia
added a commit
to dusk-network/node-installer
that referenced
this pull request
Feb 29, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Any services registered may introduce an implementation of
Initializein which method any major components/structs/resources can be fully instantiated. On implementingInitialize, ChainSrv instantiatesAcceptorstruct by which it can revert to last final state before spawningDataBrokerservice.