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

config errors to stdout #46

Closed
bradanlane opened this issue Jul 5, 2016 · 5 comments
Closed

config errors to stdout #46

bradanlane opened this issue Jul 5, 2016 · 5 comments

Comments

@bradanlane
Copy link

Currently most errors are sent to stdout. It would see to be easier to diagnose if errors (config and runtime) went to stderr.

Is there a historical or functional reason for what goes to stdout vs stderr?

@chrisdebian
Copy link

@bradanlane , you make a good point, do you know whether this is still the situation?

Chris

@bradanlane
Copy link
Author

I have not used direwolf since about 2018 so I can not speak to code enhancements over the past 8 years.

@chrisdebian
Copy link

Thanks, @bradanlane . Looks like I don't have permission to close this.

@dranch
Copy link
Collaborator

dranch commented Mar 28, 2025

Why are we seeing a rash of ticket discussion updates from topics back in 2016?!

@wb2osz
Copy link
Owner

wb2osz commented Mar 29, 2025

Almost a decade old.
Closing.
Reopen if you think something still needs to be addressed.

@wb2osz wb2osz closed this as completed Mar 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants