-
Notifications
You must be signed in to change notification settings - Fork 3k
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
ESP8266: implements possibility to decide between non-blocking/blocking connect. #9421
ESP8266: implements possibility to decide between non-blocking/blocking connect. #9421
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a single question to the switch-case statement. Otherwise a very good and helpful change :)
@VeijoPesonen, thank you for your changes. |
Ci started |
Test run: SUCCESSSummary: 11 of 11 test jobs passed |
Any of you to review this patch ? It's ready for integration |
Adding the non-blocking connect itself. @kjbracey-arm, @michalpasztamobica, @SeppoTakalo please re-review. |
CI started |
Blocking mode connect is not supported anymore when this patch is applied
Implements NetworkInterface::set_blocking() and implements the functionality to distinguish between the two in connect()
Test run: FAILEDSummary: 3 of 7 test jobs failed Failed test jobs:
|
CI aborted until review is completed |
CI started (travis restarted as well) |
Test run: FAILEDSummary: 2 of 11 test jobs failed Failed test jobs:
|
CI job restarted: Failure appeared unrelated to PR. |
CI restarted |
Description
Checks for already existing connection when trying to set credentials for a new connection or when trying to call connect. This is done to avoid the situation where an already established connection would get disrupted.
Implements possibility to decide between non-blocking/blocking connect.
Pull request type
Reviewers
@SeppoTakalo
@michalpasztamobica
@marcuschangarm
@karsev
@teetak01