leptos: Leptos Axum Handle Server Fn unwrapping Context can panic under load

Describe the bug In leptox_axum handle_server_fns_inner there are several call to unwrap() that can evidently be None (though I’m not entirely sure how).

 // If ResponseOptions are set, add the headers and status to the request
                        let res_options = use_context::<ResponseOptions>();

                        // if this is Accept: application/json then send a serialized JSON response
                        let accept_header = headers
                            .get("Accept")
                            .and_then(|value| value.to_str().ok());
                        let mut res = Response::builder();

                        // Add headers from ResponseParts if they exist. These should be added as long
                        // as the server function returns an OK response
                        let res_options_outer = res_options.unwrap().0;  -----> unwrap a none
                        let res_options_inner = res_options_outer.read();

called `Result::unwrap()` on an `Err` value: Canceled
thread '<unnamed>' panicked at .cargo/registry/src/index.crates.io-6f17d22bba15001f/leptos_axum-0.5.4/src/lib.rs:323:61: 

Leptos Dependencies

leptos = { version = "0.5", features = ["nightly"] }
leptos_axum = { version = "0.5", optional = true }
leptos_meta = { version = "0.5", features = ["nightly"] }
leptos_router = { version = "0.5", features = ["nightly"] }

To Reproduce Steps to reproduce the behavior: You’ll have to bear with me here because I can only reproduce this when stress testing.

1. run your benchmarking tool of choice ./wrk -t 8 -c 2000 -d 30s --latency http://localhost:3000
2. go anywhere on your app that makes a call to a server fn (and has IO like a database call or sleep) and uses extractors).
3. start spamming refresh until error reaching server to call server function: TypeError: NetworkError when attempting to fetch resource..

Expected behavior Option::unwrap() call is removed and replaced with a guard. Though I’m not sure what is causing this problem.

Screenshots If applicable, add screenshots to help explain your problem.

Additional context If you look at the handler you can clearly see that provide_context is called early on so there’s no reason to suspect that getting the context for ResponseOptions wouldn’t return Some, but it does). My guess bet is that there’s reads and writes going on at the same time.