-
Notifications
You must be signed in to change notification settings - Fork 746
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
Config for web3signer keep-alive #5007
Conversation
3f45967
to
9006974
Compare
Although there may be better approaches than these flags, we have one Lido operator reporting success with these flags on Holesky, to the point where they are requesting custom builds of Lighthouse release that include this change. I think we may as well include this in The flag they are using is |
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
@Mergifyio queue |
✅ The pull request has been merged automaticallyThe pull request has been merged automatically at 8fb6989 |
* Allow tweaking connection pool settings * Build docker image * Fix imports * Merge tag 'v4.6.0' into web3signer-keep-alive v4.6.0 * Delete temp docker build stuff * Fix tests * Merge remote-tracking branch 'origin/unstable' into web3signer-keep-alive * Update CLI text
Issue Addressed
Addresses #4439 in the context of web3signer connections.
One of the large staking pools was having issues with web3signer connections failing with
IncompleteMessage
errors.Proposed Changes
Additional Info
I'm not sure if this is the best way to solve this. Requiring the node operator to fiddle with yet more CLI flags is bad from a UX PoV. We may be better off adopting automatic retry.