Close SSL sockets when connections/validations fail #3318
Merged
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.
Fixes #3317
Pull Request check-list
Please make sure to review and check all of these items:
Note
CI may fail, as it currently does on the
master
branch, but because the SSL sockets are getting closed, theResourceWarning
displayed as pytest exits are now resolved.NOTE: these things are not required to open a PR and can be done
afterwards / while the PR is open.
Description of change
As noted in #3317, there are two places where SSL sockets might not get closed, and they both stem from a
RedisError
getting raised when either of two validation checks fail. This PR addresses the issue in these ways:RedisError
is now caught in addition toOSError
so the first open socket can be closed