-
Notifications
You must be signed in to change notification settings - Fork 3.4k
watcher: Avoid using global default slog #35702
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
Conversation
54166e1
to
6031f83
Compare
/test |
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.
Thanks! I looks a bit weird having to pass the logger everywhere, but I agree it seems the least friction path for the moment, without requiring a large refactoring that is definitely out of scope here.
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 minus Marco's comments 🚀
Manually removing ready-to-merge label to give @sayboras a chance to address Marco's comments before merging. |
Thanks a lot 👍 |
As highlighted in below comment, the default logger is completely replaced (rather than being mutated) during the configuration phase, so we should avoid using global slog instance. Relates: #35567 Reported-by: Marco Iorio <marco.iorio@isovalent.com> Signed-off-by: Tam Mach <tam.mach@cilium.io>
6031f83
to
6be5b67
Compare
/test |
As highlighted in below comment, the default logger is completely replaced (rather than being mutated) during the configuration phase, so we should avoid using global slog instance.
Relates: #35567
Reported-by: Marco Iorio marco.iorio@isovalent.com