Skip to content
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

Chromedriver status on Windows 10 ready not started #649

Open
vicotec opened this issue Nov 27, 2024 · 0 comments
Open

Chromedriver status on Windows 10 ready not started #649

vicotec opened this issue Nov 27, 2024 · 0 comments

Comments

@vicotec
Copy link

vicotec commented Nov 27, 2024

System: Windows 10
Symfony: 6.4
Panther: 2.1.1

I'm creating my client like this:
$client = static::createPantherClient([], [
'webdriver.server_url' => 'http://127.0.0.1:9515',
]);
and manually start the chromedriver beforehand with "chromedriver.exe --port=9515", because nothing else worked for me.

Not sure if it is a bug or bad configuration on my side.
When i create a chromeclient the process status is checked here:
Symfony\Component\Panther\ProcessManager\ChromeManager->start() which calls
Symfony\Component\Process->isRunning()
This checks against self::STATUS_STARTED which expects 'started', but my chromedriver always returns 'ready'.
So it checks the port which is not available, since the chromedriver is using it and it fails with "The port %d is already in use."
If i just disable the check, everything seems to be working fine.

The debug information for the process in the start() function looks like this for me

Symfony\Component\Process\Process {#449
-callback: null
-commandline: array:2 [
0 => "./drivers\chromedriver.EXE"
1 => "--port=9515"
]
-cwd: "D:\path\to\project"
-env: []
-input: null
-starttime: null
-lastOutputTime: null
-timeout: null
-idleTimeout: null
-exitcode: null
-fallbackStatus: []
-processInformation: ? array
-outputDisabled: false
-stdout: null
-stderr: null
-process: null
-status: "ready"
-incrementalOutputOffset: 0
-incrementalErrorOutputOffset: 0
-tty: false
-pty: false
-options: array:2 [
"suppress_errors" => true
"bypass_shell" => true
]
-processPipes: ? Symfony\Component\Process\Pipes\WindowsPipes|Symfony\Component\Process\Pipes\UnixPipes
-latestSignal: null
-cachedExitCode: null
}

The commandline path for the driver looks problematic as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant