-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
dgram: remove unreachable connectState assign #38590
Conversation
Another thing which needs to check is that calling AFAICT it doesn't, but it is better to check again in the code review. |
@pd4d10 Can you rebase against master? (so that we might have luck to get a green CI) |
It looks like there are some relevant CI failure. Also could you rebase instead of marging? Merge commits tend to break our tooling. |
The CI is green now. /cc @nodejs/dgram for more reviews. |
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.
lgtm
Landed in 5753eb1 |
PR-URL: #38590 Reviewed-By: Ouyang Yadong <[email protected]> Reviewed-By: Matteo Collina <[email protected]>
PR-URL: nodejs#38590 Reviewed-By: Ouyang Yadong <[email protected]> Reviewed-By: Matteo Collina <[email protected]>
PR-URL: #38590 Reviewed-By: Ouyang Yadong <[email protected]> Reviewed-By: Matteo Collina <[email protected]>
PR-URL: #38590 Reviewed-By: Ouyang Yadong <[email protected]> Reviewed-By: Matteo Collina <[email protected]>
PR-URL: #38590 Reviewed-By: Ouyang Yadong <[email protected]> Reviewed-By: Matteo Collina <[email protected]>
PR-URL: #38590 Reviewed-By: Ouyang Yadong <[email protected]> Reviewed-By: Matteo Collina <[email protected]>
isConnected()
returnstrue
implies thatremoteAddress()
doesn't throw an error. The implementation ofremoteAddress
is as follows:node/lib/dgram.js
Lines 770 to 775 in 29f1b60
It also implies that
state.connectState === CONNECT_STATE_CONNECTED
.So it seems not necessary to assign it again.