-
Notifications
You must be signed in to change notification settings - Fork 47
account recovery: increase default number of keys to try #436
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
This commit fixes an issue where a large number of attempts at creating an account lead to the index of the first successful account to be higher than the previous number of keys we tried by default. This resulted in the account not being recovered without manually overriding this value in the command line.
This commit fixes an issue where the derivation index of an account was greater than the default number of keys we attempted during account recovery.
positiveblue
left a comment
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.
Thanks 🙏
| RUN apt-get update && apt-get install -y git | ||
| ENV GOCACHE=/tmp/build/.cache | ||
| ENV GOMODCACHE=/tmp/build/.modcache | ||
| ENV GOFLAGS="-buildvcs=false" |
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.
should we add it to the dockerfile in the same way that is done in the other projects?
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.
Do you mean the git config --global --add safe.directory /build? (We fixed it a number of times, not sure which one actually fixes what).
To be hones, this seems clearer as it directly fixes the issue and makes it more clear that it's a Golang issue (that might be fixed in the future), rather than implying it was some sort of git problem. I can go ahead and fix it in all other repos in this manner.
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.
fixes the issue and makes it more clear that it's a Golang related issue 🥇
Do not fix it in all the other repos, I will change them and tag you in the PR 👍
ffranr
left a comment
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.
Thank you!
Fixes lightninglabs/lightning-terminal#470.
Pull Request Checklist
used.