-
-
Notifications
You must be signed in to change notification settings - Fork 856
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
Check disconnections on connection reacquiry #145
Check disconnections on connection reacquiry #145
Conversation
Raise ConnectionClosedByRemote and handle on `send`
I've pulled in a last little bit of extra work on top of this in #145 which I think is now good to go. One particularly interesting point from @njsmith, here #143 (comment)
Okay, that's an interesting case. 😑 I'd suggest we start by getting this change in as it stands. We can the confirm if we need to finesse the specific |
Should we open a separate issue to handle the 408 case? |
Yeah, defo. On it. |
Released as 0.6.8 |
Check for connection aliveness on re-acquiry from connection pool.
Superseeds #143
Great work on this @yeraydiazdiaz! There was a last little bit of extra cleanup on the connection pool handling that we can do now, which it made sense for me to pick up. I think we're good to go on this one now.