#[cfg(test)]
mod tests {
use super::*;
#[tokio::test]
async fn test_check_auth_valid() {
let mut req = Request::new(());
let token: MetadataValue<_> = "Bearer some-secret-token".parse().unwrap();
req.metadata_mut().insert("Authorization", token);
let result = check_auth(req);
assert!(result.is_ok());
}
}
The test panics with the following message when inserting the metadata value:
---- actor::grpc::tests::test_check_auth_valid stdout ----
thread 'actor::grpc::tests::test_check_auth_valid' panicked at /Users/eee/.cargo/registry/src/index.crates.io-6f17d22bba15001f/http-0.2.12/src/header/name.rs:1270:13:
index out of bounds: the len is 0 but the index is 0
The panic disappears if the insert command is removed, but obviously fails because it depends on it.
I'm failing to understand how insert is panicking here.
Bug Report
Version
Description
When creating a simple test case for the authentication interceptor example:
The test panics with the following message when
insert
ing the metadata value:The panic disappears if the
insert
command is removed, but obviously fails because it depends on it.I'm failing to understand how
insert
is panicking here.