[🚀 Feature]: [rust] Stream Selenium Manager logs to console

[nvborisenko]

Feature and motivation

Selenium manager process can be executed with --debug flag, and then process output can be redirected to internal logs. Each time, when the process outputs a message in json format, we can translate it to .net logs.

Usage example

User will be able to see SM output in his log handlers (Console, File).

[github-actions]

@nvborisenko, 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!

[titusfortner]

@nvborisenko this is the same as what the other bindings are doing, correct? Thanks.

[nvborisenko]

I guess no. Here I am expecting that each log event, produced by SM, can be routed to the internal logging in binding, real-time.

I also observed that SM doesn't output log messages in real-time..

[titusfortner]

Yeah, I think we decided that it was more trouble than it was with to try to do it real time.

[titusfortner]

Should we close this and revisit if we decide to change SM?

[nvborisenko]

Up to you, I just proposed a feature.

[titusfortner]

Hmm, it's worth being tracked I think. I'm not sure I understood the STDOUT/STDERR differentiation until Simon explained it a few weeks ago. There is probably an improvement here that SM can make.

[titusfortner]

This would be fixed by #13414

[github-actions]

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.