Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Lifecycle finalized events triggered before starting the node #1210

Open
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

Apollon77
Copy link
Collaborator

We should finalize/migrate ACL before we start the node. Also useful for other cases when we need to have these in the final data to make sure wwe do not change after someone already tries to connect.

We should finalize/migrate ACL before we start the node. Also useful for other cases when we need to have these in the final data to make sure wwe do not change after someone already tries to connect.
Copy link

semanticdiff-com bot commented Sep 19, 2024

Review changes with SemanticDiff.

Analyzed 3 of 3 files.

Overall, the semantic diff is 2% smaller than the GitHub diff.

Filename Status
✔️ packages/node/src/node/NodeLifecycle.ts Analyzed
✔️ packages/node/src/behaviors/access-control/AccessControlServer.ts 5.63% smaller
✔️ packages/node/src/behavior/system/network/ServerNetworkRuntime.ts Analyzed

@Apollon77 Apollon77 marked this pull request as ready for review September 19, 2024 14:19
/**
* Emits when the node is finalized and goes online next
*/
get finalized() {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm wondering if we can avoid adding the event, it doesn't seem very general purpose. Why do we initialize AccessControlManager when the node comes online rather than when AccessControlServer initializes?

Is it just because FabricManager isn't available until the node is online, and we need that to perform the upgrade from 0.7? In my ClientNode branch I pulled FabricManager initialization into node startup, so if that's the problem maybe I could push that so AccessManager initialization could happen sooner.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants