grunt.util.spawn should handle --debug and --debug-brk to prevent port reusing

[segrey]

Currently, if grunt main process is started with --debug-brk=<debug port> (or --debug=<debug port>), grunt.util.spawn inherits this cli option and starts child process with the same debug port. Thus, the spawned child process fails to start, because the specified debug port is already bound (by the main grunt process).
Possible fix could be to find an available port (if the main grunt process is started in debug mode) and specify the found free port when spawning the child process. Thanks!

[segrey]

JFYI, I've filed similar, but a bit more generic issue in nodejs project: nodejs/node#4419
If it gets fixed there, this issue can be closed.

[inthegarage]

Hi Segrey,

That issue is now fixed, what is the status of this issue therefore?

[segrey]

Yep, closing.

[inthegarage]

Thanks Segrey, Do you know when this will be available? I've tried 5.10.1 and the port 0 is still rejected. I've tried debug-port=0 and debug-brk=0 all to no avail.

[segrey]

I think nodejs/node#5025 should be tracked