-
-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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]: PySelenium doesn't support a named pipe as a log file #10703
Comments
@vringar, 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! |
By checking the error returned when trying to open the file with `a+` and only using `w` when it is a pipe, there is no change in behaviour wrt the common path Fixes SeleniumHQ#10703
By checking the error returned when trying to open the file with `a+` and only using `w` when it is a pipe, there is no change in behaviour wrt the common path Fixes SeleniumHQ#10703
Looks like you already have the code; please PR your proposed changes and discuss whatever impact it might have on existing users. We have a *lot of work planned in Python for 4.3. |
Also, conceptually, is this a bug, or effectively a feature request to support another type of output? |
Hmm, I was unsure about that as well. I just picked the bug report because it allowed me to show that the desired behavior is currently not supported. |
Done
I have done that in the PR. Should I do it here as well? |
Thanks @vringar seems ok to me, we could expose the |
By checking the error returned when trying to open the file with `a+` and only using `w` when it is a pipe, there is no change in behaviour wrt the common path Fixes SeleniumHQ#10703
By checking the error returned when trying to open the file with `a+` and only using `w` when it is a pipe, there is no change in behaviour wrt the common path Fixes SeleniumHQ#10703
This change allows users to specify how they want to open their log file with a fallback to `a+` if nothing else is specified Fixes SeleniumHQ#10703
This change allows users to specify how they want to open their log file with a fallback to `a+` if nothing else is specified Fixes SeleniumHQ#10703
This change allows users to specify how they want to open their log file with a fallback to `a+` if nothing else is specified Fixes SeleniumHQ#10703
This change allows users to specify how they want to open their log file with a fallback to `a+` if nothing else is specified Fixes SeleniumHQ#10703
This issue is stale because it has been open 280 days with no activity. Remove stale label or comment or this will be closed in 14 days. |
This issue was closed because it has been stalled for 14 days with no activity. |
I think I have a solution for this one that I'm working on. |
This PR ^^ will let you create the file ahead of time and pass it in rather than having to mess with tuples. |
I'm hoping to merge #12030 today I just added docs for all the languages to show which languages support what logging options — https://www.selenium.dev/documentation/webdriver/drivers/service/#console-output So we can prioritize fixing things |
Implemented via #12103 |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
What happened?
As part of OpenWPM we use Selenium to drive multiple Firefox browsers in parallel.
To capture, enrich and redirect the browser's logging output, we use named pipes that look like normal log files to Selenium.
However pipes don't support seeking so the need to be opened with
w
and not witha+
as thefirefox.Service
currently does. We have previously monkeypatched this but that approach has led to us breaking every time a new Selenium release comes out. A newer approach that tries to callfirefox.Service.__init__
and open thelog_file
afterwards doesn't work at all, so I wanted to check if there was an appetite to address this issue upstream.How can we reproduce the issue?
Relevant log output
Operating System
Linux
Selenium version
Python 4.1.0
What are the browser(s) and version(s) where you see this issue?
Firefox 100
What are the browser driver(s) and version(s) where you see this issue?
GeckoDriver 0.30.0
Are you using Selenium Grid?
No response
The text was updated successfully, but these errors were encountered: