-
Notifications
You must be signed in to change notification settings - Fork 6
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
Targetmanager doesn't need timer reset #114
Conversation
Signed-off-by: Bruno Bressi <bruno.bressi@telekom.de>
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
@puffitos Are you sure this was correct? We have timers here, not tickers. Each operation (refreshing targets, registering, and updating) now only executes once after startup. After that, the select statement blocks indefinitely because none of the channels ( As you can see in these logs, each operation is now only triggered once:
|
Thanks, I'll change those to tickers. This is the price of trusting your tests too much... |
Motivation
The reset timers are unnecessary. The timers carry on automatically and there is no need to reset them.
Changes
Removed the reset call from the timers.
TODO