Closed jonleighton closed 1 week ago
@jonleighton, thank you for creating this issue. We will troubleshoot it as soon as we can.
Triage this issue by using labels.
If information is missing, add a helpful comment and then I-issue-template
label.
If the issue is a question, add the I-question
label.
If the issue is valid but there is no time to troubleshoot it, consider adding the help wanted
label.
If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C),
add the applicable G-*
label, and it will provide the correct link and auto-close the
issue.
After troubleshooting the issue, please add the R-awaiting answer
label.
Thank you!
Thank you so much @jonleighton for raising this, I will pick this up and investigate later today
This is my draft PR to fix the issue #14433, I will improve the test later today and put it up for review
What happened?
An error from a remote Selenium server is not correctly reported when using the selenium-webdriver v4.23.0 library in Ruby.
It appears that a bug in the selenium-webdriver exception handling code causes another exception to be raised.
Note that this problem does not occur in the previous v4.22.0 version.
How can we reproduce the issue?
I can reproduce by deliberately creating a situation where the client cannot obtain a new session within the timeout.
In one terminal, start selenium via a Docker container:
In another terminal, run the following Ruby script:
Relevant log output
Operating System
macOS Sonoma
Selenium version
Ruby 4.23.0
What are the browser(s) and version(s) where you see this issue?
Chromium 127.0
What are the browser driver(s) and version(s) where you see this issue?
ChromeDriver 127.0.6533.119
Are you using Selenium Grid?
No response