-
-
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]: Fairly meaningless backtrace information is added at the expense of backtrace locations. #13221
Comments
@ioquatix, 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! |
I would like to contribute! Are there any maintainers that would be willing to review/accept my work? |
We are happy to receive contributions. For Ruby, @titusfortner can help review. |
This issue is looking for contributors. Please comment below or reach out to us through our IRC/Slack/Matrix channels if you are interested. |
@titusfortner I will try to continue the work that @ioquatix my PR is a first attempt at bug fixing this so whenever it gets reviewed I will do the changes accordingly |
Fixed in #14170 |
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?
This line of code here:
selenium/rb/lib/selenium/webdriver/remote/response.rb
Line 72 in 240e17b
Exception#backtrace_locations
to returnnil
.This is problematic for test frameworks that use the detailed information in
backtrace_locations
to format errors more effectively.In addition, the actual information that is added to the backtrace seems less than useful.
I understand the intention of this "feature" but I think significantly more is lost than is gained by including the backtrace from the web server. At present, this is causing my test harness to blow up as it expects
backtrace_locations
to at least not benil
.How can we reproduce the issue?
Any code that triggers an error from the Chrome browser, e.g. finding an element that doesn't exist.
Relevant log output
Operating System
Arch Linux
Selenium version
Ruby selenium-webdriver-4.15.0
What are the browser(s) and version(s) where you see this issue?
Chromium 119.0.6045.159 Arch Linux
What are the browser driver(s) and version(s) where you see this issue?
ChromeDriver 119.0.6045.159 (eaa767197fa7dd412133d1b84f7eb60da43409c9-refs/branch-heads/6045@{#1327})
Are you using Selenium Grid?
No response
The text was updated successfully, but these errors were encountered: