-
Notifications
You must be signed in to change notification settings - Fork 30k
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: socket.send without address fails with weird error on 5.7 #5398
Labels
confirmed-bug
Issues with confirmed bugs.
dgram
Issues and PRs related to the dgram subsystem / UDP.
Milestone
Comments
mafintosh
added a commit
to mafintosh/dns-socket
that referenced
this issue
Feb 23, 2016
cc @mcollina |
Yes it was me. Here is the infringing lines: https://github.com/nodejs/node/blob/master/lib/dgram.js#L298-L299. Thanks @Fishrock123 for routing this. |
good catch @mafintosh |
4 tasks
mcollina
added a commit
to mcollina/node
that referenced
this issue
Feb 27, 2016
Fixes a regression introduced by: nodejs#4374. Adds a new test to avoid similar issue in the future. Fixes: nodejs#5398
4 tasks
Fishrock123
pushed a commit
that referenced
this issue
Mar 2, 2016
Fixes a regression introduced by: #4374. Adds a new test to avoid similar issue in the future. The test is disabled on windows, because this feature never worked there. Fixes: #5398 Reviewed-By: Roman Reiss <me@silverwind.io> Reviewed-By: Rod Vagg <rod@vagg.org> Reviewed-By: Evan Lucas <evanlucas@me.com>
mcollina
added a commit
to mcollina/node
that referenced
this issue
Mar 4, 2016
In net we default to 'localhost' as the default address for connect. Not doing the same on dgram is confusing, because sending to 0.0.0.0 works on Linux/OS X but not on Windows. Defaulting that to 127.0.0.1 / ::1 addresses that. Related: nodejs#5407 Related: nodejs#5398 Fixes: nodejs#5487
mcollina
added a commit
that referenced
this issue
Mar 5, 2016
In net we default to 'localhost' as the default address for connect. Not doing the same on dgram is confusing, because sending to 0.0.0.0 works on Linux/OS X but not on Windows. Defaulting that to 127.0.0.1 / ::1 addresses that. Related: #5407 Related: #5398 Fixes: #5487 PR-URL: #5493 Reviewed-By: Saúl Ibarra Corretgé <saghul@gmail.com> Reviewed-By: Roman Reiss <me@silverwind.io>
Fishrock123
pushed a commit
that referenced
this issue
Mar 8, 2016
In net we default to 'localhost' as the default address for connect. Not doing the same on dgram is confusing, because sending to 0.0.0.0 works on Linux/OS X but not on Windows. Defaulting that to 127.0.0.1 / ::1 addresses that. Related: #5407 Related: #5398 Fixes: #5487 PR-URL: #5493 Reviewed-By: Saúl Ibarra Corretgé <saghul@gmail.com> Reviewed-By: Roman Reiss <me@silverwind.io>
Fishrock123
pushed a commit
that referenced
this issue
Mar 8, 2016
In net we default to 'localhost' as the default address for connect. Not doing the same on dgram is confusing, because sending to 0.0.0.0 works on Linux/OS X but not on Windows. Defaulting that to 127.0.0.1 / ::1 addresses that. Related: #5407 Related: #5398 Fixes: #5487 PR-URL: #5493 Reviewed-By: Saúl Ibarra Corretgé <saghul@gmail.com> Reviewed-By: Roman Reiss <me@silverwind.io>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
confirmed-bug
Issues with confirmed bugs.
dgram
Issues and PRs related to the dgram subsystem / UDP.
On node 4.x and node <5.7 this worked
With node 5.7 this fails with
The dgram docs on both 4.x and 5.x say
The text was updated successfully, but these errors were encountered: