Closed Cookie-Monster-Coder closed 3 years ago
NOTE THAT UNCLEAR BUG REPORTS (i.e. without the information requested below like logs, settings, versions, etc) MIGHT BE CLOSED WITHOUT ANY HELP!!
Please check https://github.com/wouterdebie/locast2tuner/releases if any breaking changes have been made before filing a bug report.
Describe the bug locast2tuner won't start and exits with an error.
To Reproduce Steps to reproduce the behavior:
Logs
Aug 27 02:40:00.387 INFO locast2tuner 0.3.10 on Linux 5.4.0-81-generic (Docker) starting.., Aug 27 02:40:00.387 DEBG Main UUID: 7ce65969-bbca-4cf3-8a1d-dc2ef24e25a0, Aug 27 02:40:00.387 INFO Consider sponsoring this project at https://github.com/sponsors/wouterdebie!, Aug 27 02:40:00.387 DEBG Logging in with xxxxxxxx@gmail.com.com, Aug 27 02:40:00.395 DEBG starting new connection: https://api.locastnet.org/, Aug 27 02:40:00.400 TRCE registering event source with poller: token=Token(1), interests=READABLE | WRITABLE, Aug 27 02:40:00.709 TRCE signal: Want, Aug 27 02:40:00.709 TRCE signal found waiting giver, notifying, Aug 27 02:40:00.709 TRCE poll_want: taker wants!, Aug 27 02:40:00.828thread 'main ' panicked at 'TRCELogin failed ', signal: Wantsrc/credentials.rs:, 73:14, Aug 27 02:40:00.828note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace, TRCE signal: Want, Aug 27 02:40:00.828 DEBG response '204 No Content' for https://api.locastnet.org/api/user/login?client_id=i7XBbuDLYwN%2Bd%2Bcf84YQCYK-NyR8QjBGyFV-g5zCRFY%3D, thread 'main' panicked at 'slog-scope: No logger set. Use `slog_scope::set_global_logger` or `slog_scope::scope`.', /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/slog-scope-4.4.0/lib.rs:125:13, stack backtrace:, 0: 0x7f3d3fc71be0 - <unknown>, 1: 0x7f3d3fcb250c - <unknown>, 2: 0x7f3d3fc6b835 - <unknown>, 3: 0x7f3d3fc73c1b - <unknown>, 4: 0x7f3d3fc736f1 - <unknown>, 5: 0x7f3d3fc742e4 - <unknown>, 6: 0x7f3d3f792944 - <unknown>, 7: 0x7f3d3f7927ec - <unknown>, 8: 0x7f3d3f65c13c - <unknown>, 9: 0x7f3d3f7924b9 - <unknown>, 10: 0x7f3d3f791d58 - <unknown>, 11: 0x7f3d3f791b80 - <unknown>, 12: 0x7f3d3fc59cf6 - <unknown>, 13: 0x7f3d3f96c2cf - <unknown>, 14: 0x7f3d3f9865a6 - <unknown>, 15: 0x7f3d3f98ff97 - <unknown>, 16: 0x7f3d3fa1a33f - <unknown>, 17: 0x7f3d3fa1ac3c - <unknown>, 18: 0x7f3d3f9e3dfb - <unknown>, 19: 0x7f3d3f965bbd - <unknown>, 20: 0x7f3d3f99cd6f - <unknown>, 21: 0x7f3d3f9ac880 - <unknown>, 22: 0x7f3d3f702ba2 - <unknown>, 23: 0x7f3d3f6de6a1 - <unknown>, 24: 0x7f3d3f69050c - <unknown>, 25: 0x7f3d3f691268 - <unknown>, 26: 0x7f3d3f69cef8 - <unknown>, 27: 0x7f3d3f68b24a - <unknown>, 28: 0x7f3d3f6c2a32 - <unknown>, 29: 0x7f3d3fc74859 - <unknown>, 30: 0x7f3d3f69cf32 - <unknown>, thread panicked while panicking. aborting., /app/run.sh: line 13: 8 Illegal instruction (core dumped) /app/locast2tuner -b 0.0.0.0 $config
Configuration l2t_days=2 l2t_override_zipcodes=xxxxx l2t_password=xxxxxxxxxxxxx l2t_username=xxxxxxxx@gmail.com PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin l2t_verbose=3 l2t_RUST_BACKTRACE=1
Environment Ubuntu 20.04 running locast2tuner in docker
NOTE THAT UNCLEAR BUG REPORTS (i.e. without the information requested below like logs, settings, versions, etc) MIGHT BE CLOSED WITHOUT ANY HELP!!
Please check https://github.com/wouterdebie/locast2tuner/releases if any breaking changes have been made before filing a bug report.
Describe the bug locast2tuner won't start and exits with an error.
To Reproduce Steps to reproduce the behavior:
Logs
Configuration l2t_days=2 l2t_override_zipcodes=xxxxx l2t_password=xxxxxxxxxxxxx l2t_username=xxxxxxxx@gmail.com PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin l2t_verbose=3 l2t_RUST_BACKTRACE=1
Environment Ubuntu 20.04 running locast2tuner in docker