Rocket.rs dev seems broken, vaultwarden fails to launch

Help
1

yesterday I built vaultwarden from source and got this error:

[2021-10-13 08:26:50.348][panic][ERROR] thread ‘main’ panicked at ‘Error: expected token ‘/’ but found ‘b’ at index 0’: /opt/bitwarden_rs/.cargo/git/checkouts/rocket-8bf16d9ca7e90bdc/263e39b/core/lib/src/rocket.rs:528
0: vaultwarden::init_logging::{{closure}}
1: std::panicking::rust_panic_with_hook
at /rustc/5a7834050f3a0ebcd117b4ddf0bc1e8459594309/library/std/src/panicking.rs:626:17
2: std::panicking::begin_panic_handler::{{closure}}
at /rustc/5a7834050f3a0ebcd117b4ddf0bc1e8459594309/library/std/src/panicking.rs:519:13
3: std::sys_common::backtrace::__rust_end_short_backtrace
at /rustc/5a7834050f3a0ebcd117b4ddf0bc1e8459594309/library/std/src/sys_common/backtrace.rs:141:18
4: rust_begin_unwind
at /rustc/5a7834050f3a0ebcd117b4ddf0bc1e8459594309/library/std/src/panicking.rs:515:5
5: std::panicking::begin_panic_fmt
at /rustc/5a7834050f3a0ebcd117b4ddf0bc1e8459594309/library/std/src/panicking.rs:457:5
6: rocket::rocket::rocket::mount::{{closure}}
7: rocket::rocket::rocket::mount
8: vaultwarden::main
9: std::sys_common::backtrace::__rust_begin_short_backtrace
10: std::rt::lang_start::{{closure}}
11: core::ops::function::impls::<impl core::ops::function::FnOnce for &F>::call_once
at /rustc/5a7834050f3a0ebcd117b4ddf0bc1e8459594309/library/core/src/ops/function.rs:259:13
std::panicking::try::do_call
at /rustc/5a7834050f3a0ebcd117b4ddf0bc1e8459594309/library/std/src/panicking.rs:401:40
std::panicking::try
at /rustc/5a7834050f3a0ebcd117b4ddf0bc1e8459594309/library/std/src/panicking.rs:365:19
std::panic::catch_unwind
at /rustc/5a7834050f3a0ebcd117b4ddf0bc1e8459594309/library/std/src/panic.rs:434:14
std::rt::lang_start_internal::{{closure}}
at /rustc/5a7834050f3a0ebcd117b4ddf0bc1e8459594309/library/std/src/rt.rs:45:48
std::panicking::try::do_call
at /rustc/5a7834050f3a0ebcd117b4ddf0bc1e8459594309/library/std/src/panicking.rs:401:40
std::panicking::try
at /rustc/5a7834050f3a0ebcd117b4ddf0bc1e8459594309/library/std/src/panicking.rs:365:19
std::panic::catch_unwind
at /rustc/5a7834050f3a0ebcd117b4ddf0bc1e8459594309/library/std/src/panic.rs:434:14
std::rt::lang_start_internal
at /rustc/5a7834050f3a0ebcd117b4ddf0bc1e8459594309/library/std/src/rt.rs:45:20
12: main
13: __libc_start_main
14: _start

I believe this is because rocket.rs=0.5.0-dev is broken, would it not make more sense to specify =0.5.0-rc1 in the Cargo.toml file to make sure builds are working?
2

We use a very specific git commit checksum, so it can’t be broken because of that. At least, not because of code changes regarding Rocket.

If you use the master branch of Vaultwarden as-is it compiles fine for me. It could be some external libraries, but not sure.

3

Hi,

Yes, I just noticed lower in the Cargo.toml file there is a patch that pins the commit of rocket,
This was indeed a configuration issue, a bit sad to see a simple forgotten ‘/’ in a configuration file result in a full on panic, but things worked after fixing my configuration.