-
Notifications
You must be signed in to change notification settings - Fork 117
Open
Description
Hi,
I am facing an issue where I am getting a panic from hdrhistogram on a long running request. The request completes in about ~7 seconds, however, even when usin the --timout 15 flag I am still seeing the below panic. I am not sure why this is occuring but wondering if it may be that the response is too large. But the request is succeding with a 200 response, but the overall test fails with the below panic.
The response is in json format.
The reponse is 320537 bytes long.
Example response:
{
"count": 1,
"amassData": [
{
"key": {
"runId": "4f8aef08-2049-4544-97d1-224519170bd2",
"amassId": "3b23a290-1d2e-4561-b1af-0a3269a9e91d",
"type": "amass"
},
"value": {
"subDomains": [
"sum.domain.com",
"sum2.domain.com",
....,
}
}
}
Exception message
Error connecting 'http://localhost:3005/api/data/amass?runId=4f8aef08-2049-4544-97d1-224519170bd2': reqwest::Error { kind: Request, url: Url { scheme: "http", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("localhost")), port: Some(3005), path: "/api/data/amass", query: Some("runId=4f8aef08-2049-4544-97d1-224519170bd2"), fragment: None }, source: TimedOut }
thread 'main' panicked at /home/jmoney/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/hdrhistogram-7.5.4/src/lib.rs:1864:28:
called `Result::unwrap()` on an `Err` value: ValueOutOfRangeResizeDisabled
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Metadata
Metadata
Assignees
Labels
No labels