-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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, unix socket bind should be only used in passive mode #373
Conversation
Good catch! please also make the same change to |
Also, I wonder why the system call - bind() didn't raise an error when it's called by client socket. |
the client of gnet is sync using built in |
You're right, I forgot that. Now please apply the same code changes to the other files. |
ok, I foget :( |
… fd for EINPROGRESS error when connecting
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.
Please take a look at these review comments.
Codecov Report
@@ Coverage Diff @@
## dev #373 +/- ##
==========================================
- Coverage 72.04% 71.36% -0.69%
==========================================
Files 13 13
Lines 1381 1390 +9
==========================================
- Hits 995 992 -3
- Misses 318 326 +8
- Partials 68 72 +4
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
Thanks~ |
@ccssrryy |
The error check is in |
name: Pull request
about: Propose changes to the code
title: ''
labels: ''
assignees: ''
1. Are you opening this pull request for bug-fixes, optimizations or new feature?
bug-fixes
2. Please describe how these code changes achieve your intention.
unix socket bind should be only used in passive mode
When using non-blocking socket as client, we should not close fd for EINPROGRESS error
3. Please link to the relevant issues (if any).
4. Which documentation changes (if any) need to be made/updated because of this PR?
4. Checklist