-
-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ panic] isahc panicked at 'called Result::unwrap()
on an Err
#424
Comments
cause:
code in fn register:
|
Thanks for filing an issue! I'll take a deeper look into this when I am able. At a cursory glance, the key part of this error is that the cause is an Also, which operating system are you experiencing this error on? That might help lead me into the right direction. |
Could you share an example program that reproduces this problem? That would also be very helpful. You wouldn't happen to be using |
@sagebind Thank you very much!
This problem is sporadic. I run this on many machines and only one machine's application was crashed caused by this panic. Maybe at that point, something (such as network or hard disk) went wrong? |
Hello, I'm facing the same problem as @txgj when using isahc, with the same error message:
The application is using the The app is running on a container inside a k8s cluster, and the problem as @txgj mentioned is sporadic Is there an investigation going on for this problem ? Thanks :) |
@men1n2 This issue is the investigation. 😄 I cannot promise any sort of timeline for fixing this, but I will be looking into it over the next week or so to try and identify the problem. Right now I don't even know what the cause of this might be so it might be a little while before I can identify a fix. |
thread 'isahc-agent-0' panicked at 'called
Result::unwrap()
on anErr
value: Os { code: 1, kind: PermissionDenied, message: "..." }', /root/.cargo/registry/src/github.aaakk.us.kg-1ecc6299db9ec823/isahc-1.7.2/src/agent/mod.rs:548:68note: run with
RUST_BACKTRACE=1
environment variable to display a backtraceThe text was updated successfully, but these errors were encountered: