-
-
Notifications
You must be signed in to change notification settings - Fork 8.1k
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]: Running chrome driver with --remote-debugging-pipe makes dev_tools unavailable in ruby #13979
Comments
@tubaxenor, 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! |
@tubaxenor, then do not add the flag? If it is the expected behavior, we cannot do much about it. |
I see, but still wondering if there a way to obtain devtools connection from pipe... The best I can get is the source code here: https://source.chromium.org/chromium/chromium/src/+/main:content/browser/devtools/devtools_pipe_handler.cc Which seems like it's using internal thread to make the connection but would like to have some 👀 to double check there is not much we can do before closing this issue 🙇 |
You should probably reach out to the Chrome team to find out if there is a way to do that. |
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?
Passing
--remote-debugging-pipe
as chrome driver options removesdebuggerAddress
setting and causedriver.devtools
to raise error.This is expected behavior in chromedriver: https://chromium.googlesource.com/chromium/src/+/master/chrome/test/chromedriver/test/run_py_tests.py#5959
How can we reproduce the issue?
Relevant log output
The text was updated successfully, but these errors were encountered: