-
-
Notifications
You must be signed in to change notification settings - Fork 232
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
Warnings printed to stderr, --no-warning partially ignored #2083
Comments
For I agree that |
For our CI purposes, as long as --no-warning silences the warnings we don't care too much where they'd get printed otherwise, so if changing that (even for --validate only) is problematic I'm okay just not doing it. |
@poshul a fix for |
Expected Behavior
Warnings should be printed to stdout not stderr. --no-warning should silence warnings
Actual Behavior
warnings are printed to stderr. passing --no-warning does not silence warnings.
Example output:
with
--no-warning
without
--no-warning
:The text was updated successfully, but these errors were encountered: