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

[FEATURE] Add Environment Variable DISABLE_STDOUT to Suppress Terminal Output #6060

Open
dwisiswant0 opened this issue Feb 20, 2025 · 0 comments · May be fixed by #6058
Open

[FEATURE] Add Environment Variable DISABLE_STDOUT to Suppress Terminal Output #6060

dwisiswant0 opened this issue Feb 20, 2025 · 0 comments · May be fixed by #6058
Assignees
Labels
Type: Enhancement Most issues will probably ask for additions or changes.

Comments

@dwisiswant0
Copy link
Member

Describe your feature request

Add an option to completely suppress stdout output by introducing an environment variable DISABLE_STDOUT. When set to "true" or "1", this option ensures that no output is printed to the terminal.

Describe the use case of the feature

This feature is useful in scenarios where a clean and quiet terminal is required, such as benchmarking or automated testing (w/o SDK). For instance, when running a benchmark on RunEnumeration, suppressing event output helps in collecting accurate metrics without unnecessary clutter.

Describe alternatives you've considered

  • Redirecting types.Options.Output to /dev/null: This approach does not fully suppress output, likely due to the presence of a multi-writer handling the output.
  • Manually filtering output after execution: This is impractical and adds unnecessary complexity.
  • Modifying the code to bypass writing to stdout: While possible, it would require changes in multiple places, making it less flexible than a simple environment variable.

Additional context

No response

@dwisiswant0 dwisiswant0 added the Type: Enhancement Most issues will probably ask for additions or changes. label Feb 20, 2025
@dwisiswant0 dwisiswant0 self-assigned this Feb 20, 2025
@dwisiswant0 dwisiswant0 linked a pull request Feb 20, 2025 that will close this issue
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Enhancement Most issues will probably ask for additions or changes.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant