when run with "-d" option, triggers "Could not determine the UTC offset on this system" error

[njskalski]

Steps to reproduce: install and run as in docs, but with "-d" flag, and then try to update index from a project actually using the cached mirror. On my machine it resulted in "Could not determine the UTC offset on this system"

thread '<unnamed>' panicked at 'Could not determine the UTC offset on this system. Possible causes are that the time crate does not implement "local_offset_at" on your system, or that you are running in a multi-threaded environment and the time crate is returning "None" from "local_offset_at" to avoid unsafe behaviour. See the time crate's documentation for more information. (https://time-rs.github.io/internal-api/time/index.html#feature-flags): IndeterminateOffset', /home/andrzej/.cargo/registry/src/github.com-1ecc6299db9ec823/simple_logger-1.16.0/src/lib.rs:409:85
stack backtrace:
   0: rust_begin_unwind
             at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/std/src/panicking.rs:584:5
   1: core::panicking::panic_fmt
             at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/core/src/panicking.rs:142:14
   2: core::result::unwrap_failed
             at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/core/src/result.rs:1805:5
   3: <simple_logger::SimpleLogger as log::Log>::log
   4: log::__log
   5: logger::Logger::log
   6: <logger::Logger as iron::middleware::AfterMiddleware>::after
   7: iron::middleware::Chain::continue_from_before
   8: <iron::middleware::Chain as iron::middleware::Handler>::handle
   9: <iron::iron::RawHandler<H> as hyper::server::Handler>::handle
  10: hyper::server::Worker<H>::handle_connection
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

I guess an update to logger or simplifying output format might help