-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
"Never return 'WOULD BLOCK' on a non-blocking socket" #528
Labels
archived
Do not use - historically applied to archived issues
bug
component-platform
Portability layer and build scripts
help-wanted
This issue is not being actively worked on, but PRs welcome.
Comments
ARM Internal Ref: IOTSSL-863 |
Can you explain what you issue is here? |
I guess the reporter meant this typo in the comments.
It should be
|
@harmv I agree, that makes perfect sense. |
RonEld
added
archived
Do not use - historically applied to archived issues
help-wanted
This issue is not being actively worked on, but PRs welcome.
and removed
tracking
labels
Jun 13, 2019
Patater
added a commit
to Patater/mbedtls
that referenced
this issue
Jun 19, 2019
Patater
added a commit
to Patater/mbedtls
that referenced
this issue
Jun 19, 2019
Patater
added a commit
to Patater/mbedtls
that referenced
this issue
Jun 20, 2019
Patater
added a commit
to Patater/mbedtls
that referenced
this issue
Jun 20, 2019
Patater
added a commit
to Patater/mbedtls
that referenced
this issue
Jun 20, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
archived
Do not use - historically applied to archived issues
bug
component-platform
Portability layer and build scripts
help-wanted
This issue is not being actively worked on, but PRs welcome.
Comment seen in net_would_block()
The text was updated successfully, but these errors were encountered: