-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Refactor port detection code #113
Comments
A better option would be to get phantomjs to report the actual port used On Sat, Jan 16, 2016 at 8:28 AM, Vitaly Puzrin [email protected]
|
Ah, you are right. Alternative is to completely drop this code, when 2.0 available. Forgot about it :) Current situation is, that phantom 2.0 can not be installed on linux via npm. This problem is known, old, and nobody can say when it will be solved. So, i did not tried to investigate what's up with port in 2.0. |
Just for records. Reports about bad |
https://github.com/Medium/phantomjs/releases/tag/v2.1.1 Holy shit! PhantomJS 2.1 finally available on npm for linux! |
Update 2.1.2 works somehow, but:
Will continue tomorrow. |
Nothing changed about port in 2.1. Created issue ariya/phantomjs#13947 |
Good news - issue assigned for 2.2 release |
Should this be targeting |
Current port detection code tries to be compact and simple. As a result - logic partially goes to shell, and becomes messy.
Ideas:
update
-p
key are related to docker busybox images. Can be solved by install full version of netstat/ssThe text was updated successfully, but these errors were encountered: