-
Notifications
You must be signed in to change notification settings - Fork 249
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
fix: proper usage of CreateAccount RootDataDir #5284
Conversation
Jenkins BuildsClick to see older builds (20)
|
1a4543e
to
697e2be
Compare
Hey @igor-sirotin! Thanx for the PR. Could you please clarify, does this branch still valid #5255 or we should continue testing this new branch? Seems both branches a linked to the same issue #5186 |
@pavloburykh sorry for confusing. I closed #5284 now. |
no worries, thank you for clarification @igor-sirotin |
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.
LGTM!
@igor-sirotin thanks for the PR, no issues from mobile side. Tested in status-im/status-mobile#20316 What has been tested:
|
22eec2c
to
bdccd5d
Compare
bdccd5d
to
020d422
Compare
* fix_: introduce CreateAccount.RootDataDir * fix_: deprecate and remove ShhextConfig.BackupDisabledDataDir
* fix_: introduce CreateAccount.RootDataDir * fix_: deprecate and remove ShhextConfig.BackupDisabledDataDir
Closes #5186
CreateAccount.BackupDisabledDataDir
CreateAccount.RootDataDir
(with fallback toBackupDisabledDataDir
until both clients update)nodeConfig.ShhextConfig.BackupDisabledDataDir
to./
by defaultloadNodeConfig
and stop on errorShhextConfig.BackupDisabledDataDir
. It was only used once as RootDataDir. Which was wrong and very confusing.