-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Using zapcore.Level less than -1 and sampling causes a panic #713
Comments
Would you be interested in others implementing it? |
I don't think we want to add any more levels to zap, I've found that users aren't even sure when to use the current set of levels. I think adding more levels increases complexity, so we'd need to be convinced of the benefit before adding additional levels (or allowing custom levels). |
As there has been little movement on this issue, I am going to close it. If someone would like to drive it we can either re-open or create a duplicate. |
When someone sets the
zapcore.Level(-2)
with sampling set to true, there is a panic.I was wondering if it makes sense to allow for this configuration by disabling sampling for any logs that are below the set debug level.
Original Issue:
go-logr/zapr#2
/cc @DirectXMan12
The text was updated successfully, but these errors were encountered: