Fix DagCallback not working when using gitbundle #61178
Closed
+267
−5
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
In cases where the dag processor component is run in a separate container/pod, dag callback does not work for git dag bundle. This is because the dagbag could not find the exact version to use in running the callback since the versioned repo is not created in the dag processor. The fix here is to create the versioned repo in the dag processor. In the process, we also need to ensure that the stale bundles are cleaned
jedcunningham
requested changes
Jan 29, 2026
Member
There was a problem hiding this comment.
This isn't a GitDagBundle problem. You'd have to do this for every bundle that supports versioning!
Instead, the dag processor should init a bundle at the right version if a callback ends up coming in. Just like workers do when starting a task.
Member
|
Closes: #52040 |
Member
|
#60734 is the right fix for this problem. |
Contributor
Author
|
Closing in favour of #60734 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
In cases where the dag processor component is run in a separate container/pod, dag callback does not work for git dag bundle. This is because the dagbag could not find the exact version to use in running the callback since the versioned repo is not created in the dag processor.
The fix here is to create the versioned repo in the dag processor. In the process, we also need to ensure that the stale bundles are cleaned
Was generative AI tooling used to co-author this PR?
{pr_number}.significant.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.