Skip to content
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

server: disable DNS boostrap for SigNet nodes #5564

Merged
merged 3 commits into from
Aug 5, 2021

Conversation

Roasbeef
Copy link
Member

In this commit, we fix a bug that would cause nodes attempting to run
using the signet chain, to waste CPU as they attempted to boostrap to a
non-existent DNS seed. We fix this by ignoring the DNS boostrapper is
signet is active. Along the way, we refactor the conditional sightly to
be more readable, and easily extensible.

@Roasbeef Roasbeef added config Parameters/arguments/config file related issues/PRs bug fix labels Jul 24, 2021
@Roasbeef Roasbeef added this to the v0.14.0 milestone Jul 24, 2021
Copy link
Member

@yyforyongyu yyforyongyu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM⚡️

Not sure how we manage our release notes tho. Do we need to update it in almost every PR?

server.go Outdated
!(s.cfg.Bitcoin.SimNet || s.cfg.Litecoin.SimNet) &&
!(s.cfg.Bitcoin.RegTest || s.cfg.Litecoin.RegTest) {

isSimnet := (s.cfg.Bitcoin.SimNet || s.cfg.Litecoin.SimNet)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🥳

@Roasbeef
Copy link
Member Author

Not sure how we manage our release notes tho. Do we need to update it in almost every PR?

With how things are rn, yeh we effectively need to each time. I want to double back on this and add a simple unit test as well, just to lock things down a bit more.

In this commit, we fix a bug that would cause nodes attempting to run
using the signet chain, to waste CPU as they attempted to boostrap to a
non-existent DNS seed. We fix this by ignoring the DNS boostrapper is
signet is active. Along the way, we refactor the conditional sightly to
be more readable, and easily extensible.
@Roasbeef Roasbeef merged commit da1d022 into lightningnetwork:master Aug 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug fix config Parameters/arguments/config file related issues/PRs
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants