Clear autoregistered DAGs if there are any import errors #26398
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
We need to clear any autoregistered DAGs that may have been already registered if we encounter any import errors while parsing a given DAG file. This maintains the behavior before we autoregistered DAGs.
jedcunningham
force-pushed
the
clear_autoregistered_dags_on_import_error
branch
from
934c912 to
9d7f4b8
Compare
ashb
approved these changes
Sep 14, 2022
jedcunningham
added a commit
that referenced
this pull request
Sep 15, 2022
We need to clear any autoregistered DAGs that may have been already registered if we encounter any import errors while parsing a given DAG file. This maintains the behavior before we autoregistered DAGs. (cherry picked from commit 01e3fb7)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
We need to clear any autoregistered DAGs that may have been already registered if we encounter any import errors while parsing a given DAG file.
This maintains the behavior before we autoregistered DAGs.