21:57 <sharkdp> achin: In https://github.com/sharkdp/numbat/pull/511, I removed the "local-timezone" Cargo feature that you introduced recently. I *think* everything should work out of the box now.

21:59 <sharkdp> triallax: That PR also solves https://github.com/sharkdp/numbat/issues/344, which I had already closed. Numbat now uses the systems timezone database (typically /usr/share/zoneinfo/)

22:00 <sharkdp> (on Windows and in WASM builds for the web, tzdata is still embedded into the binary though)

22:03 <achin> ok. my use-case was about building wasi components, which is not a build that we typically do (the wasm builds for the web are wasm32-unknown-unknown)

22:04 <achin> and most wasm runtimes/wasi hosts don't yet have a way to expose timezone info, so this probably doesn't work

22:05 <achin> though there's been a lot of movement on this recently including with BurntSushi : https://github.com/WebAssembly/wasi-clocks/issues/69

22:14 <sharkdp> Yes, but jiff will now simply fall back to UTC for wasm-wasi, as long as there is no support for exposing timezone info

22:15 <sharkdp> iana-time-zone did not distinguish between different wasm32-*-* targets, but jiff does.

22:20 <achin> ok, that sounds like exactly the behavior we want, nice