debug broken on 0.19.0 but works on 0.18.1

[elgalu]

I'm unable to debug on protractor 0.19.0

Failed to open socket on port 5858, waiting 1000 ms before retrying

Downgraded to protractor 0.18.1 and worked fine!
Then re-installed 0.19.0 to test again, and the same socket error.

Tested on chrome33 & firefox27, chromedriver 2.9. node 0.10.25
Using webdriver-manager start in another console.

$ protractor debug config/local/firefox.js
< debugger listening on port 5858
connecting... ok
break in /usr/local/lib/node_modules/protractor/lib/cli.js:7
  5  * Values from command line options override values from the config.
  6  */
  7 'use strict';
  8 
  9 // Coffee is required here to enable config files written in coffee-script.
debug> c
< ------------------------------------
< PID: 15196 (capability: firefoxANY #1)
< ------------------------------------
< debugger listening on port 5858
< Failed to open socket on port 5858, waiting 1000 ms before retrying
< Failed to open socket on port 5858, waiting 1000 ms before retrying
< Failed to open socket on port 5858, waiting 1000 ms before retrying
< Failed to open socket on port 5858, waiting 1000 ms before retrying
< Failed to open socket on port 5858, waiting 1000 ms before retrying
< Failed to open socket on port 5858, waiting 1000 ms before retrying

Then port 5858 seems to be left open:

$ sudo lsof -i tcp:5858
COMMAND   PID USER   FD   TYPE  DEVICE SIZE/OFF NODE NAME
node    15185 user   11u  IPv4 1397240      0t0  TCP localhost:58131->localhost:5858 (ESTABLISHED)
node    15187 user    9u  IPv4 1397907      0t0  TCP localhost:5858 (LISTEN)
node    15187 user   10u  IPv4 1395469      0t0  TCP localhost:5858->localhost:58131 (ESTABLISHED)
node    15196 user    9u  IPv4 1397907      0t0  TCP localhost:5858 (LISTEN)
node    15196 user   10u  IPv4 1395469      0t0  TCP localhost:5858->localhost:58131 (ESTABLISHED)

Please note debug works well when i re-install 0.18.1

Tried with a remote selenium grid, same issue so webdriver-manager is not related.

#549 looks like a question but might be related.

[sJhonny]

yup, same here- doesn't work on 0.19 (although i don't see those socket errors), seems to be working with 0.18.1

[mcalthrop]

I get the above error using both 0.19.0 and 0.18.1.

[elgalu]

@mcalthrop ensure you kill all node processes before trying again on 0.18.1

[mcalthrop]

Thanks Leo, good call – correction: debugging works on 0.18.1, but on 0.19.0 I get the error described above.

[elgalu]

i'm glad to help narrowing this issue :)

[mcalthrop]

Yep, definitely don't want any red herrings!

I hope this bug gets picked up soon. Making it hard to debug.

[juliemr]

On the radar! Thanks for pointing this out!

[chris-ramon]

That's right! debugger is working on 0.18.1, however i had to change chromeDriver within protractor config file, because I was getting an error about path.

chromeDriver: '../node_modules/protractor/selenium/chromedriver'

[juliemr]

Fix is in - should be out next release. Thanks for your patience, everyone.

[dineshdh]

The issue still seems to be present in version 0.20.1. I am running protractor with the debug param, but the test completes successfully and competently ignores the line which says browser.debugger();