-
Notifications
You must be signed in to change notification settings - Fork 43
Jon/fix/zano private view key await #960
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
Conversation
44660e4
to
bee0726
Compare
bee0726
to
b362e3a
Compare
b362e3a
to
cf54a4b
Compare
cf54a4b
to
50303fb
Compare
50303fb
to
a81130c
Compare
a81130c
to
74463fa
Compare
74463fa
to
ff0324c
Compare
711ef0d
to
05880a9
Compare
05880a9
to
db795b7
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll go ahead and rebase this branch with my own fixes, rather than leaving a more-detailed review. I know you are swamped with other tasks.
24e5eb8
to
62f3924
Compare
This deadlock doesn't actually occur, since many methods can trigger the initial |
Not a bug. The contract with the core says the keys will be present. Otherwise, it is a genuine error. |
- Manages resources that need to start/stop at random times - Prevents multiple instances running simultaneously - Handles state transitions: stopped → starting → started → stopping - Provides error handling and cleanup on failures - Generic utility that could be useful for other engines
- Replace direct zanoWalletId tracking with LifecycleManager pattern - Add ALREADY_EXISTS error handling for wallet reinitialization - Fix getDisplayPublicSeed to wait for wallet initialization - Improve error logging and recovery for existing wallets - Use getOpenedWallets() to find existing wallet by storage path
95428c0
to
aa589cf
Compare
CHANGELOG
Does this branch warrant an entry to the CHANGELOG?
Dependencies
noneDescription
none