-
Notifications
You must be signed in to change notification settings - Fork 187
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
Add Robust Support for Callbacks at Task and TaskGroup Level #322
Merged
Merged
Changes from all commits
Commits
Show all changes
32 commits
Select commit
Hold shift + click to select a range
5ea61fd
Unit-tests added for Tasks/TaskGroups
jroach-astronomer a4d3456
Refactored unit-tests, ready to go
jroach-astronomer 46b58b3
Stashing changes for syncing fork
jroach-astronomer 484058d
Updating example_callbacks.yml file
jroach-astronomer 25baecc
Removing placeholders
jroach-astronomer 81b8c7d
Resolving MC
jroach-astronomer a1d15a2
Resolving merge conflict
jroach-astronomer cb6ad85
Fixing unit tests
jroach-astronomer 1635b1b
Pre-commit checks
jroach-astronomer 5cc8a87
Stashing changes for the night
jroach-astronomer 8c31635
on_skipped_callback removing from default_args
jroach-astronomer 32a7400
Version management for Slack
jroach-astronomer f626458
Adding un-added files
jroach-astronomer 7df1861
Version check for on_skipped_callback
jroach-astronomer 4c9ab09
Updating unit-tests
jroach-astronomer 8688408
Updating unit-tests
jroach-astronomer 9a7d058
Updating unit-tests
jroach-astronomer d5d8e68
Updating unit-tests
jroach-astronomer fc26000
Updating unit-tests
jroach-astronomer 05db194
Updating unit-tests
jroach-astronomer 975efe0
Updating unit-tests
jroach-astronomer 7710f31
Updating unit-tests
jroach-astronomer 7a79fd5
Updating unit-tests
jroach-astronomer ca9d1cb
Updating unit-tests
jroach-astronomer 196420f
Linting, adding version-checking
jroach-astronomer add2786
Adding action-items to tests for versioning
jroach-astronomer c4a2342
Added test-coverage for #253
jroach-astronomer 197e8de
Updated example DAG, unit tests
jroach-astronomer a0e0bca
Merge branch 'main' into issue-253
jroach-astronomer 27b336b
Merge branch 'main' into issue-253
jroach-astronomer 060b96a
Adjusted example DAG to ensure that callback parameters were successf…
jroach-astronomer 317b35e
Merge branch 'main' into issue-253
pankajkoti File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I’m wondering if we should continue supporting the
{callback_type}_name
+{callback_type}_file
approach for callbacks. Are there scenarios where simply specifying{callback_type}
might be insufficient or lack necessary support?Unifying the approach to a single, straightforward method seems more maintainable and less confusing for users. Additionally, what happens if a user specifies both
on_success_callback
andon_success_callback_name + on_success_callback_file
? Currently, it appears thaton_success_callback_name + on_success_callback_file
will override theon_success_callback
, which isn’t transparent to the end user and could cause confusion.While this isn’t part of your changes and has been a pre-existing issue, it might be worth discussing whether we could drop support for the
name+file
approach altogether or at least an error when users try to provide callbacks using both approaches. What do you think?