Closed martin-braun closed 1 year ago
Trace logging is only enabled in a debug build, by design: so that we can not be afraid of making trace logging calls in code hot paths (when in a non-debug build, the trace call is a no-op).
@jagerman Thanks a lot. I wasn't able to pin-point the location where this is happening, but it kinda makes sense. You guessed it right, I was testing with a release build.
Describe the bug
--log-level trace
will only logdebug
and notrace
messages, although the daemon reports "Setting log level to trace". Also giving a wrong log level will just exit the storage server without any printed message, because it tries to log a critical error about the wrong log level before the logger has been initialized.So far, I couldn't pin point the root for the main issue (
oxenss
oroxen-logger
).To Reproduce
oxen-storage --log-level trace
Desktop (please complete the following information):