log4rs panics when conf file doesn't exist about log4rs HOT 4 CLOSED

Is it panicking or just printing the error message? At least running the test crate with the log config moved does not cause a panic but does print the error message out.

from log4rs.

I suspect it's panicking, but I'll have a second look at my code. I defined a match against the Result from init_file, but it's not being executed (as far as I can tell; I'll have a look with LLDB), hence my assumption.

from log4rs.

I see what the problem is now. My panic was coming from somewhere else. That being said, init_file always returns Ok, even if the file is not found, which might not be what the user expects.

from log4rs.

This is just a suggestion: If it will always return Ok, wouldn't it make sense to default to a stdout fallback with only the root logger with an info level?

Also, perhaps it would be better to collect the Errs it encounters during initialisation and return them, instead of printing them to stderr.

Thanks again, and sorry about a false alarm.

from log4rs.