Skip to content
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

Fix for #1813 - don't actually connect to a null endpoint #2042

Merged
merged 1 commit into from
Mar 17, 2022

Conversation

NickCraver
Copy link
Collaborator

We log this, but then forgot to abort, woops. Actually bail in this case, no reason to rapidly issue sockets to nowhere.

We log this, but then forgot to abort, woops. Actually bail in this case, no reason to rapidly issue sockets to nowhere.
@NickCraver NickCraver merged commit d62b015 into main Mar 17, 2022
@NickCraver NickCraver deleted the craver/fix-1813 branch March 17, 2022 00:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Incorrectly configured Redis server silently causes hundreds of first-chance exceptions per minute
2 participants