Skip to content

[🚀 Feature]: Leverage streaming output in the bindings #13989

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.

Sign up for GitHub

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

Jump to bottom
Open
titusfortner opened this issue May 20, 2024 · 5 comments
Open

[🚀 Feature]: Leverage streaming output in the bindings #13989

titusfortner opened this issue May 20, 2024 · 5 comments
Labels
C-dotnet .NET Bindings C-java Java Bindings C-nodejs JavaScript Bindings C-py Python Bindings C-rb Ruby Bindings I-enhancement Something could be better
Milestone
Selenium 5.0

Comments

@titusfortner
Copy link
Member

titusfortner commented May 20, 2024 •
edited
Loading

Status

  • Ruby —
  • Python —
  • Java —
  • .NET —
  • JS —

Feature and motivation

Now that #13260 has been implemented with #13414 we need each of the bindings to

  1. switch from --output json to --output mixed
  2. leverage [🚀 Feature]: Selenium Manager Log Level #13437 and use --log-level rather than --debug
  3. switch from printing logged output at the end of the selenium manager execution to using the streamed output

Usage example

./selenium-manager --browser chrome --log-level debug --output mixed
@titusfortner titusfortner added C-py Python Bindings C-rb Ruby Bindings C-dotnet .NET Bindings C-java Java Bindings C-nodejs JavaScript Bindings I-enhancement Something could be better labels May 20, 2024
@titusfortner titusfortner added this to the Selenium 5.0 milestone May 20, 2024
@aguspe
Copy link
Contributor

aguspe commented Jun 24, 2024

@titusfortner is there help wanted for the ruby bindings for this feature?

@titusfortner
Copy link
Member Author

Sure!

@aguspe aguspe mentioned this issue Jun 25, 2024
Merged
8 tasks
@github-actions GitHub Actions
Copy link

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.

@github-actions github-actions bot added the J-stale Applied to issues that become stale, and eventually closed. label Dec 31, 2024
@github-actions GitHub Actions
Copy link

This issue was closed because it has been stalled for 14 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jan 14, 2025
@github-actions GitHub Actions
Copy link

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 Feb 13, 2025
@nvborisenko nvborisenko reopened this Feb 14, 2025
@nvborisenko nvborisenko removed the J-stale Applied to issues that become stale, and eventually closed. label Feb 14, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
C-dotnet .NET Bindings C-java Java Bindings C-nodejs JavaScript Bindings C-py Python Bindings C-rb Ruby Bindings I-enhancement Something could be better
Projects
None yet
Milestone
Selenium 5.0
Development

No branches or pull requests
3 participants
@titusfortner @nvborisenko @aguspe