fix: collect all NoNodeForYamlKey errors instead of stopping at first when using --warn-error-options#12564
Open
kalluripradeep wants to merge 1 commit intodbt-labs:mainfrom
Open
Conversation
… when using --warn-error-options
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
1 participant
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.
Fixes #12339
What changed
When using
--warn-error-options '{"error": ["NoNodeForYamlKey"]}',dbt was only surfacing the first missing node error and stopping.
All subsequent patches in the YAML were never processed.
Root cause
In
PatchParser.parse(),warn_or_error()raisesEventCompilationErrorimmediately on the first missing node, exiting the loop early.
Fix
Wrapped
self.parse_patch()in atry/except EventCompilationErrorblock so the loop continues, collects all errors, and raises them
together at the end.