wttrbar giving a panic result
gnussbaum67 opened this issue · comments
Logged in just now and noticed that weather wasn't showing. Tried running wttrbar in a terminal and got a panic. I used RUST_BACKTRACE=full and got this:
[$] <> RUST_BACKTRACE=full wttrbar
thread 'main' panicked at src/main.rs:61:64:
called Result::unwrap() on an Err value: reqwest::Error { kind: Decode, source: Error("expected value", line: 1, column: 1) }
stack backtrace:
0: 0x5973ab0614d5 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::h367d587903c05733
1: 0x5973ab086abb - core::fmt::write::h90d6c7093938e590
2: 0x5973ab05e96f - std::io::Write::write_fmt::hf166be129b5ac403
3: 0x5973ab0612ae - std::sys_common::backtrace::print::h16f4e54dda428f87
4: 0x5973ab062569 - std::panicking::default_hook::{{closure}}::h421dd5e2264b9ca7
5: 0x5973ab0622ad - std::panicking::default_hook::hd6ec143ee36c91c5
6: 0x5973ab062a03 - std::panicking::rust_panic_with_hook::he0e1ddfdd1ef8a31
7: 0x5973ab0628e4 - std::panicking::begin_panic_handler::{{closure}}::h75fca2fc3c1ec62d
8: 0x5973ab061999 - std::sys_common::backtrace::__rust_end_short_backtrace::h9d480d72ed19fe3c
9: 0x5973ab062617 - rust_begin_unwind
10: 0x5973aadca4a3 - core::panicking::panic_fmt::h10c3ee83b4e55229
11: 0x5973aadca956 - core::result::unwrap_failed::h635713c629d81684
12: 0x5973aadce94d - wttrbar::main::h3eab8b0daf843a7d
13: 0x5973aade8976 - std::sys_common::backtrace::__rust_begin_short_backtrace::h2075f8f060ba5aba
14: 0x5973aade23ec - std::rt::lang_start::{{closure}}::h90594ae5817e8d19
15: 0x5973ab0593d0 - std::rt::lang_start_internal::h5add80e16e4e0045
16: 0x5973aadcf2f4 - main
17: 0x7643f0450c88 -
18: 0x7643f0450d4c - __libc_start_main
19: 0x5973aadcabf5 - _start
20: 0x0 -
Not sure what the issue is.
EDIT: using Arch linux and Hyprland
are you still seeing this? which version of wttrbar? is wttr.in working for you? it looks like a network issue
I'm using 0.10.5
I can double check network as I installed it on another machine and it works.
confirmed it's working. This issue can be closed.