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

HttpConnector should not error if a socket option fails #2359

Closed
seanmonstar opened this issue Dec 14, 2020 · 2 comments · Fixed by #2361
Closed

HttpConnector should not error if a socket option fails #2359

seanmonstar opened this issue Dec 14, 2020 · 2 comments · Fixed by #2361
Labels
A-client Area: client. E-easy Effort: easy. A task that would be a great starting point for a new contributor.

Comments

@seanmonstar
Copy link
Member

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).

@seanmonstar seanmonstar added A-client Area: client. E-easy Effort: easy. A task that would be a great starting point for a new contributor. labels Dec 14, 2020
@aeryz
Copy link
Contributor

aeryz commented Dec 16, 2020

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?

@seanmonstar
Copy link
Member Author

What do you propose? I think if the option is required to function, then of course error. But most aren't.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-client Area: client. E-easy Effort: easy. A task that would be a great starting point for a new contributor.
Projects
None yet
2 participants