-
Notifications
You must be signed in to change notification settings - Fork 808
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
Support legacy data directories #2846
Conversation
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.
This is way cleaner. Happy to close the other PR in favour of this one :)
Just a small nit that was also present in my PR.
@@ -66,6 +66,15 @@ impl<E: EthSpec> ProductionBeaconNode<E> { | |||
let freezer_db_path = client_config.create_freezer_db_path()?; | |||
let executor = context.executor.clone(); | |||
|
|||
if let Some(legacy_dir) = client_config.get_existing_legacy_data_dir() { | |||
warn!( |
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.
This log comes up even for the default datadir (~/.lighthouse/<network>
) which might cause unnecessary confusion. Perhaps we can skip the log for the default datadir?
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.
Ooh, good catch! No log when the legacy and default directory are the same!
Thanks @pawanjay176, I addressed your comment. Good catch! |
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!
Issue Addressed
NA
Proposed Changes
Provides an alternate to #2843.
Enables backwards compatibility for data directories created prior to #2682.
Additional Info
NA