-
-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
[🐛 Bug]: error from remote server causes a secondary error in Ruby library #14415
Comments
@jonleighton, thank you for creating this issue. We will troubleshoot it as soon as we can. Info for maintainersTriage this issue by using labels.
If information is missing, add a helpful comment and then
If the issue is a question, add the
If the issue is valid but there is no time to troubleshoot it, consider adding the
If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C),
add the applicable
After troubleshooting the issue, please add the 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 |
This issue has been automatically locked since there has not been any recent activity since it was closed. Please open a new issue for related bugs. |
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
The text was updated successfully, but these errors were encountered: