server: don't die on startup when persistent peer already connected#8865
server: don't die on startup when persistent peer already connected#8865aakselrod wants to merge 1 commit intolightningnetwork:masterfrom
Conversation
|
Important Review skippedAuto reviews are limited to specific labels. Labels to auto review (1)
Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configration File (
|
| s.cfg.ConnectionTimeout, | ||
| ) | ||
| if err != nil { | ||
| if err != nil && |
There was a problem hiding this comment.
Seems this would only happen if AddPeers had a duplicate? Or I guess if two DNS hosts return the same IP?
There was a problem hiding this comment.
I think it might be that the connection manager started just above accepted a connection from the configured peer before the attempt to add the peer from the config here. Unfortunately I can't get to the logs from before applying this fix any more to prove that this is what happened but I'll add an itest for this to make sure I'm going in the right direction. Thanks!
Change Description
Description of change / link to associated issue.
Steps to Test
Steps for reviewers to follow to test the change.
Pull Request Checklist
Testing
Code Style and Documentation
[skip ci]in the commit message for small changes.📝 Please see our Contribution Guidelines for further guidance.