-
Notifications
You must be signed in to change notification settings - Fork 46
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 on ConnectionReset #206
Comments
Thanks, do you mean it happens only when stop the service? Or when disconnecting and then reconnecting e.g. on the host machine - and if so, does it continue to work after that (if you re-connect?) It seems we just need to actually handle the possible let buffer = stream_forward.fill_buf().unwrap();
let length = buffer.len();
if buffer.is_empty() {
// Connection closed
debug!("Client closed connection");
return;
} |
when disconnecting and then reconnecting.... yeah it does seem to keep on runnin |
have you any quick fix to solve this? i now saw the thread really crashing and my service being unavailable:
dont really have any rust experience, but cant we just check for an error beforehand? |
Yeah, we can just handle the error, I'll take a look today. - it's weird that it makes it unavailable though since it should only be for that connection. I.e. if you reconnect it should be a different thread spawned, |
great thanks! do you mind publishing a new release? |
@jamesmcm ah just noticed the release github actions did not run.... |
Yeah, I will do but I need to update the dockerhub images. Github auto-closed this, I'll re-open it until it's published on the AUR, etc. |
It's released now, hopefully it fixes the issue. At least now it will definitely close the thread when the connection dies instead of unwinding the stack. |
I'm seeing this still on 0.10.6. Will try and get a full stack trace. |
|
once again thank you for this awesome tool.
sometimes when disconnecting from my service (which runs with vopono) i get:
its just a notification, everything continues to work.
anyway to gracefully handle this error within vopono?
cheers max
The text was updated successfully, but these errors were encountered: