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

Block app startup until all identities are ready from the network side #3257

Conversation

HenrikJannsen
Copy link
Contributor

@HenrikJannsen HenrikJannsen commented Mar 4, 2025

Fixes #3237

…tities to ensure that all identities are ready from the network side when the app has started up.
@HenrikJannsen HenrikJannsen changed the title Use a blocking call for supplyInitializedNode in initializeActiveIden… Block app startup until all identities are ready from the network side Mar 4, 2025
@HenrikJannsen HenrikJannsen requested a review from axpoems March 4, 2025 10:50
Copy link
Contributor

@axpoems axpoems left a comment

Choose a reason for hiding this comment

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

utACK

@HenrikJannsen HenrikJannsen merged commit 00b628d into bisq-network:main Mar 5, 2025
15 checks passed
@HenrikJannsen HenrikJannsen deleted the wait-at-app-initialisation-until-all-node-identies-are-ready branch March 7, 2025 15:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Handle case if user node initialization fails
2 participants