seems to be passing debug stdin through to selenium_webdriver with options:{debug:true}

[jdgblinq]

seems to be passing debug stdin through to selenium_webdriver with options:{debug:true}

Running "protractor:runDebug" (protractor) task
Verifying property protractor.runDebug exists in config...OK
File: [no files]
Options: configFile="../protractor.conf.js", keepAlive=false, noColor=false, debug, args={}
Options: { configFile: '../protractor.conf.js',
  keepAlive: false,
  noColor: false,
  debug: true,
  args: {} }
Spawn node with arguments: /Users/jesse/blinqmedia/facelift/facelift_frontend/node_modules/protractor/bin/protractor debug ../protractor.conf.js --verbose
Using the selenium server at http://127.0.0.1:4444/wd/hub
Hit SIGUSR1 - starting debugger agent.
debugger listening on port 5858
connecting... ok
break in timers.js:77
  75 }
  76 
  77 function listOnTimeout() {
  78   var msecs = this.msecs;
  79   var list = this;
debug> c>> Attempting to shut down selenium nicely

> > 17:12:21.588 INFO - Checking Resource aliases
> > 
> > 17:12:21.589 INFO - Command request: shutDownSeleniumServer[, ] on session null
> > 
> > 17:12:21.590 INFO - Shutdown command received
> > 
> > 17:12:21.590 INFO - initiating shutdown
> > 
> > 17:12:21.591 INFO - Got result: OK on session null
> > 
> > 17:12:22.093 INFO - Shutting down...
> > 
> > Selenium Standalone has exited with code 0
> > 
> > ```
> > ```

[jdgblinq]

To reproduce, create a protractor target named test:e2e:debug with options:{debug:true} set, then run grunt test:e2e:debug --verbose. You'll see the debug> prompt. Now press a key, and you'll see selenium standalone shut itself down.