Cleaner formatting of Aviary warnings#789
Merged
jkirk5 merged 6 commits intoOpenMDAO:mainfrom Jun 13, 2025
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Added custom formatting for warning messages Aviary produces based on verbosity level. Currently does not reformat warnings called by other modules, so migrating to a new system such as logging is the long-term solution. QUIET mode does suppress all warnings now though, regardless of which module called them.
New warning format:
Verbosityis 0 (QUIET): warnings are suppressedVerbosityis 1 (BRIEF):Warning: <warning message>- example:Warning: Missing variableVerbosityis 2 (VERBOSE):<warning_category>: <warning message>- example:UserWarning: Missing VariableVerbosityis 3 (DEBUG): default warning message, which includes traceback to filename and line number where warning is triggeredRemoved
include_landingflag from level2 as it is redundant/conflicting with the already existinginclude_landingkey in phase_infoRelated Issues
Backwards incompatibilities
None
New Dependencies
None