We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
An error trying to set a socket option should not error the entire connect attempt. Instead, they should just be logged (perhaps at warn level).
warn
The text was updated successfully, but these errors were encountered:
I am interested in this but I have a question. Should we just log all socket option failures and continue to connect? Are there any fatal ones?
Sorry, something went wrong.
What do you propose? I think if the option is required to function, then of course error. But most aren't.
fix(client): log socket option errors instead of returning error (#2361)
dad5c87
Closes #2359
fix(client): log socket option errors instead of returning error (hyp…
7226b70
…erium#2361) Closes hyperium#2359
Successfully merging a pull request may close this issue.
An error trying to set a socket option should not error the entire connect attempt. Instead, they should just be logged (perhaps at
warn
level).The text was updated successfully, but these errors were encountered: