-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
babel: Clean babel config on babel daemon stop #17685
Conversation
b08fd1d
to
552c2b7
Compare
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
babeld/babeld.c
Outdated
diversity_kind = DIVERSITY_NONE; | ||
diversity_factor = BABEL_DEFAULT_DIVERSITY_FACTOR; | ||
resend_delay = BABEL_DEFAULT_RESEND_DELAY; | ||
smoothing_half_life = BABEL_DEFAULT_SMOOTHING_HALF_LIFE; |
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.
By the way, shouldn't we use change_smoothing_half_life()
? I see it's also used to calculate two_to_the_one_over_hl
.
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.
You are right, that's the way to do it. Just fixed that.
When deactivating babel no router babel and later re-enabling it router babel the previous configuration is still in place. Steps to reproduce: - Enable babel - Configure babel - Disable babel with "no router babel" - Verify config Expected correct behavior: No config present Signed-off-by: Yaroslav Kholod <[email protected]>
552c2b7
to
58188b5
Compare
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.
Slava Ukraini 🇺🇦
Heroyam Slava |
When deactivating babel no router babel and later re-enabling it router babel the previous configuration is still in place.
Steps to reproduce:
Expected correct behavior: No config present