-
Notifications
You must be signed in to change notification settings - Fork 116
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
Command-line log-level no longer accepts categories (dev) #1619
Comments
One thing to keep in mind that might be an edge case in the current implementation: the meaning of |
Another issue: in |
Also: if it hasn't merged yet by the time you start working on this, there's a related commit (with title "Log levels: ...") that ought to be cherry-picked that makes the levels case-insensitive and adds some abbreviations to the levels list. |
Current dev introduces a few regressions in log-level handling:
The
--log-level
(orlog-level=...
in the config file) can no longer be set to a categorized string, but only to a single global level. This is really useful when debugging one particular subsystem to be able to throw it into debug logging while not getting debug logs from other bits.It looks like we do have log level parsing in logging/oxen_logger.cpp, but it seems to only be used via RPC, but isn't called by daemon/main.cpp, so this is probably just a matter of wiring it up.
Never mind, I'm wrong about this:
The numeric values given tolog-level
don't work the same as they used to: they used to map to a categorized list of levels so that level "2" would show info from some categories, warning from some.The text was updated successfully, but these errors were encountered: