Codechange: ensure OnConnect() always gets called with a valid socket #9729
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation / Problem
The backtrace in #9728 is odd to me. The only reason I can think of that
this->sock
isINVALID_SOCKET
is when theOnConnect
already indicated this. That should never happen, but two flows in the code didn't validate for it (where the other two we have did). Neither should ever beINVALID_SOCKET
, but should/would/could.Description
This might help uncover where in #9728 the socket becomes
INVALID_SOCKET
.Limitations
Checklist for review
Some things are not automated, and forgotten often. This list is a reminder for the reviewers.