Skip to content

Crash on login to Reddit via token bearer flow #111

@dotancohen

Description

@dotancohen

Bug description

$ export RUST_BACKTRACE=1; rexit messages -t
> Your Bearer Token from Matrix; https://github.com/mpult/rexit/ under Important Notice ********
2025-02-16 12:30 - INFO: Login Successful
2025-02-16 12:30 - INFO: Initializing Image Log
thread 'main' panicked at src/ReAPI/rooms.rs:58:10:
Error parsing array; likely error with login
stack backtrace:
   0: rust_begin_unwind
             at /build/rustc-ntAYxy/rustc-1.75.0+dfsg0ubuntu1/library/std/src/panicking.rs:645:5
   1: core::panicking::panic_fmt
             at /build/rustc-ntAYxy/rustc-1.75.0+dfsg0ubuntu1/library/core/src/panicking.rs:72:14
   2: core::panicking::panic_display
             at /build/rustc-ntAYxy/rustc-1.75.0+dfsg0ubuntu1/library/core/src/panicking.rs:178:5
   3: core::panicking::panic_str
             at /build/rustc-ntAYxy/rustc-1.75.0+dfsg0ubuntu1/library/core/src/panicking.rs:152:5
   4: core::option::expect_failed
             at /build/rustc-ntAYxy/rustc-1.75.0+dfsg0ubuntu1/library/core/src/option.rs:1985:5
   5: rexit::ReAPI::rooms::download_rooms::{{closure}}
   6: rexit::main::{{closure}}
   7: tokio::runtime::park::CachedParkThread::block_on
   8: tokio::runtime::context::runtime::enter_runtime
   9: tokio::runtime::runtime::Runtime::block_on
  10: rexit::main
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
  • I'll add the full backtrace to the first comment, to not pollute this bug report.

  • Would you like to work on a fix? [y/n]

No, I do not have the technical capabilities to work on a fix. But if someone wants to mentor me through it, and be patient while I learn Rust along the way, I'm happy to oblige.

To Reproduce

Steps to reproduce the behavior:

  1. Install Rexit via cargo | Build Rexit from the Main branch (I tried both)
  2. Run rexit messages -t
  3. Paste proper, working Authorization header, not including the word "Bearer".
  4. ...
  5. Profit

I am able to reproduce the bug in the main branch, too. That's the backtrace that I'll add to the first comment.

Environment

$ cat /etc/issue
Ubuntu 24.04.1 LTS \n \l

$ ./target/release/rexit -V
rexit 2.0.0

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions