Skip to content
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]: Console logs returned as zero using RemoteDriver (SeleniumGrid) .NET Selenium #14545

Closed
sponnusamyneogov opened this issue Sep 27, 2024 · 7 comments · Fixed by #14549

Comments

@sponnusamyneogov
Copy link

What happened?

This code is not functioning correctly when using RemoteWebDriver with Selenium Grid.

[Test]
public void ConsoleLogsGridRun()
{
var options = new ChromeOptions();
options.SetLoggingPreference(LogType.Browser, OpenQA.Selenium.LogLevel.All);
var Driver = new RemoteWebDriver(
new Uri("http://10.0.0.37:8888/"),
new RemoteSessionSettings(options), TimeSpan.FromSeconds(100));
Driver.Url = "https://www.selenium.dev/selenium/web/bidi/logEntryAdded.html";

Driver.FindElement(By.Id("consoleLog")).Click();
Driver.FindElement(By.Id("consoleError")).Click();

var jsErrors = Driver.Manage().Logs.GetLog(LogType.Browser);
}

Please advise

How can we reproduce the issue?

[Test]
public void ConsoleLogsGridRun()
{
var options = new ChromeOptions();
options.SetLoggingPreference(LogType.Browser, OpenQA.Selenium.LogLevel.All);
var Driver = new RemoteWebDriver(
new Uri("http://10.0.0.37:8888/"),
new RemoteSessionSettings(options), TimeSpan.FromSeconds(100));
Driver.Url = "https://www.selenium.dev/selenium/web/bidi/logEntryAdded.html";

Driver.FindElement(By.Id("consoleLog")).Click();
Driver.FindElement(By.Id("consoleError")).Click();

var jsErrors = Driver.Manage().Logs.GetLog(LogType.Browser);
}

Relevant log output

jsErrors returned as null

Operating System

Windows 10

Selenium version

Selenium Version 4.25.0

What are the browser(s) and version(s) where you see this issue?

Chrome

What are the browser driver(s) and version(s) where you see this issue?

129.0.6668.71

Are you using Selenium Grid?

Selenium Grid 4.25.0

Copy link

@sponnusamyneogov, thank you for creating this issue. We will troubleshoot it as soon as we can.


Info for maintainers

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!

@nvborisenko
Copy link
Member

Confirmed, Driver.Manage().Logs.GetLog(LogType.Browser); even doesn't make http call to a remote.

@nvborisenko
Copy link
Member

image

@diemol @pujagani do you know whether it should be supported by remote?

@nvborisenko
Copy link
Member

I found this one: w3c/webdriver#406 where it is recommended to use BiDi implementation.

Now the correct question is: should we be silent here? And don't throw exception? In my opinion we should always throw if something is not supported.

@sponnusamyneogov your way is only trying out BiDi (already available as nightly build or wait next release).

@pujagani
Copy link
Contributor

pujagani commented Oct 1, 2024

Java supports in remote so probably it should be supported too. One use case that I can think of is, users also use the Appium server with the Selenium client libraries and they will not be able to use BiDi in this case.

@nvborisenko
Copy link
Member

Then it should be implemented for RemoteWebDriver too, thanks for the info.

Copy link

github-actions bot commented Nov 2, 2024

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.

@github-actions github-actions bot locked and limited conversation to collaborators Nov 2, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants