policy: lazily start SelectorCache.handleUserNotifications #24325
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Hive wants components to not start any goroutines during startup. Change SelectorCache so that handleUserNotifications is started when the first notification is queued, not when SelectorCache is created. Signed-off-by: Lorenz Bauer <lmb@isovalent.com>
lmb
added
release-note/misc
|
Flake: #24217 |
|
/test |
|
cc @joamaki |
jrajahalme
approved these changes
Mar 13, 2023
christarazi
added
kind/enhancement
christarazi
approved these changes
Mar 13, 2023
maintainer-s-little-helper
bot
added
the
ready-to-merge
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hive wants components to not start any goroutines during startup. Change SelectorCache so that handleUserNotifications is started when the first notification is queued, not when SelectorCache is created.