-
Notifications
You must be signed in to change notification settings - Fork 313
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
Comments
@bradanlane , you make a good point, do you know whether this is still the situation? Chris |
I have not used direwolf since about 2018 so I can not speak to code enhancements over the past 8 years. |
Thanks, @bradanlane . Looks like I don't have permission to close this. |
Why are we seeing a rash of ticket discussion updates from topics back in 2016?! |
Almost a decade old. |
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?
The text was updated successfully, but these errors were encountered: