-
Notifications
You must be signed in to change notification settings - Fork 47
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
Could not determine the UTC offset on this system #51
Comments
I recommend using simple_logger::SimpleLogger::new()
.with_level(LevelFilter::Warn)
.with_module_level("filter", verbosity)
.with_utc_timestamps()
.init().unwrap(); I'm currently working out if I can replace the current |
Are you running a program that uses multiple threads, or is this happening in a single threaded application? |
this is in a multi-threaded actix (tokio) application. My main looks like this:
|
This is unfortunately expected then. I'm working out what I can do to change the defaults in #52, as this is caused by a dependency.
|
UTC timestamps are now the default in simple_logger 2.0.0. |
Fix a bug where simple_logger would not start due to time crate not providing a local timestamp. simple_logger 2.x.x now displays by default the timestamp in UTC which does not have this issue. Since we are not displaying timestamp in logs, this bump is harmless. Issue: borntyping/rust-simple_logger#51 Fix & recomendation: borntyping/rust-simple_logger#52
Fix a bug where simple_logger would not start due to time crate not providing a local timestamp. simple_logger 2.x.x now displays by default the timestamp in UTC which does not have this issue. Since we are not displaying timestamp in logs, this bump is harmless. Issue: borntyping/rust-simple_logger#51 Fix & recomendation: borntyping/rust-simple_logger#52
Using initialization code:
This occurs on a WSL2 console running debian. This is a really standard environment, perhaps the default could be to not try to localize the time instead, or fallback to another mode more gracefully.
I should also note this panic is 'new' after upgrading the library. The default mode now causes systems that previous ran to panic.
The text was updated successfully, but these errors were encountered: