Exception not handled about open_tunnel.url
MoOx opened this issue · comments
Not sure what I changed recently (just a few lines) and I am getting this
$ zuul -- dist/test.js
- testing: chrome @ Windows 2012 R2: 39 40
/.../node_modules/zuul/node_modules/zuul-localtunnel/index.js:22
var url = open_tunnel.url + '/__zuul';
^
/.../node_modules/zuul/node_modules/zuul-localtunnel/index.js:22:26,/.../node_modules/zuul/node_modules/zuul-localtunnel/node_modules/localtunnel/client.js:312:20,/.../node_modules/zuul/node_modules/zuul-localtunnel/node_modules/localtunnel/client.js:283:20,Request._callback (/.../node_modules/zuul/node_modules/zuul-localtunnel/node_modules/localtunnel/client.js:206:24),Request.self.callback (/.../node_modules/zuul/node_modules/zuul-localtunnel/node_modules/localtunnel/node_modules/request/main.js:122:22),Request.emit (events.js:110:17),Request.<anonymous> (/.../node_modules/zuul/node_modules/zuul-localtunnel/node_modules/localtunnel/node_modules/request/main.js:655:16),Request.emit (events.js:129:20)This doesn't help a lot :/
This exception is highly unexpected, so I doubt it should be handled. Do you have local changes to Zuul itself? Or just configuration / the tests?
Hmm the issue itself looks like for some reason localtunnel is unable to open a tunnel.
I just get the same issue on travis :/ (so fresh zuul module)
@MoOx ok that just happened to me too. I think there's something wrong with localtunnel.
Without making any changes that is.
Good to know the issue is not just for me.
But ouch.
So I am guessing this case should be handled :(
Should probably be handled in the localtunnel module though.
zuul-localtunnel, sure.
You'll see
Error: localtunnel server returned an error, please try again
from now on.
@MoOx looks like lt is back! :)
I just pinged the interested person on twitter ;)