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
GODRIVER-2881 Enable logging for ComponentAll #1340
Conversation
name: "component mismatch", | ||
logger: Logger{ | ||
ComponentLevels: map[Component]Level{ | ||
ComponentCommand: LevelDebug, | ||
}, | ||
}, | ||
level: LevelDebug, | ||
component: ComponentTopology, |
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.
I think it will be better to have want
explicitly.
internal/logger/logger_test.go
Outdated
name: "nil", | ||
want: false, |
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.
I think it will be better to have all zero values explicitly.
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.
Awesome!
GODRIVER-2881
Summary
Update the considerations for enabling a log to
Background & Motivation
There is a logging design oversight in which enabling logging with "options.LogComponentAll" does not result in the publication of logs. This issue arises because the "LevelComponentEnabled" method on the internal logger object fails to account for this specific use case.