-
Notifications
You must be signed in to change notification settings - Fork 785
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 incorrect VC default HTTP token path when the --datadir
flag is present
#6748
Conversation
0a9b7dc
to
3e8935b
Compare
3e8935b
to
eeb3916
Compare
This wasn't included in the v6.0.1 release, so a patch isn't required 😌 |
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.
Took me a while to see the difference. Nice catch!
@mergify requeue |
❌ This pull request head commit has not been previously disembarked from queue. |
@mergify queue |
✅ The pull request has been merged automaticallyThe pull request has been merged automatically at 87b72de |
Thanks for catching this! I made a mistake in my previous contribution, and I appreciate your help in fixing it. |
All good, I missed it in review too 🙏 |
Issue Addressed
Fixes a validator client bug introduced in #6577.
When a custom
--datadir
flag is provided, the default http token path changes to$HOME/.lighthouse/mainnet/validators/api-token.txt
, rather than the previous default<datadir>/validators/api-token.txt
This causes a
CRIT
in some setups where the validator client does not have write access to the home directory (e.g.eth-docker
):Proposed Changes
Set the correct default VC API token path, if a
datadir
orvalidators-dir
is provided.