Port 0 or '?' not working on OS X

[kibin]

When I'm trying to set port to special values (e.g. 0 or '?') grunt exits with
Fatal error: Port should be > 0 and < 65536
On colleague's Ubuntu it seems to working okay.

What might be the problem?
I'm on OS X 10.9.2, grunt 0.4.4, grunt-contrib-connect 0.7.1

[vladikoff]

When I use this on OS X I get port :51103. I pushed 2 tests configurations to the repo 001dde7
See if you can npm install and npm test

[kibin]

Strange. I've cloned repo, made npm install, npm test, but still:

Running "connect:self_port_q" (connect) task
Fatal error: Port should be > 0 and < 65536
npm ERR! Test failed.  See above for more details.
npm ERR! not ok code 0

[wilmoore]

Yup, verified. Running the unit tests on OS X results in the same Fatal error: Port should be > 0 and < 65536.

[fardog]

Can verify that all tests pass on OS X, 10.9.2. I get port :62106; something else might be at play here.

rMPB 15-inch, Early 2013
Mac OS X 10.9.2
Node v0.10.26
npm v1.4.3
grunt-cli v0.1.13
grunt v0.4.4

I'm an administrator on my Mac OS X machine, but the npm test command was run without sudo so that shouldn't make any difference.

[kibin]

Okay, now I understand the problem: I've switched to node 0.10.26 and all tests have passed. However on 0.11.11 (that I had) and on the latest 0.11.13 tests are failing.

[vladikoff]

0.11.11 is not supported, it is unstable.

[jeffreydwalter]

I'm seeing this issue in node v0.12.0 on OSX 10.10.1.

$ node -v
v0.12.0
$ grunt connect
Running "connect:task" (connect) task
Fatal error: port should be > 0 and < 65536: 0

[quentindemetz]

Same issue here. @vladikoff do you want me to create a new ticket ?

[jeffreydwalter]

@quentindemetz I already filed an issue for this bug in the node project and they resolved it.

nodejs/node-v0.x-archive#9194

[quentindemetz]

Thanks, fantastic! Looks as if it's been fixed, we just need to wait for a new release…