Result::unwrap() called on Err when no server is available about mongo-rust-driver-prototype HOT 3 CLOSED

From running this code on my own machine, it appears that the unwrapping actually occurs in your own code on line 56, namely let mut cursor = collection.find(None, None).unwrap(); You can verify this by using gdb to run the actual binary file generated in the target subdirectory and setting a breakpoint at rust_panic.

One thing that's a bit subtle about Client::connect is that the errors tht it returns actually have to do with properly initializing the mutex and with creating the topology. You can look at Client::with_config (which is called by Client::connect to see the details of this.

On a slightly unrelated note, creating a new Client on every request is fairly inefficient. Client is actually just an alias of an Arc type, which means you can open the connection at the top of the function and then just use .clone() to get an (owned) atomic reference to it inside each of your routes that need it.

from mongo-rust-driver-prototype.

Thank you so much for such an informative response.
I had an uneasy feeling about creating multiple clients; I was mislead by a tutorial. Thanks for setting me straight
And I hadn't played with the debugger before posting this ticket. I see that it is indeed a fault of my own!

from mongo-rust-driver-prototype.

Thanks @saghm

from mongo-rust-driver-prototype.