-
Notifications
You must be signed in to change notification settings - Fork 14.6k
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
Improve stability of remove_task_decorator function #38649
Improve stability of remove_task_decorator function #38649
Conversation
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.
Thanks for the fix, even did not know about this bug. Thanks also for the TODO; I assume there should be better options to parse the source code other than cutting by keywords.
Thanks for reviving this old PR, I totally forgot about it but I'm glad to see that its back up for review 🙌 FWIW I still think that this is an imperfect solution (and anything which relies on manipulating code as a plain string probably will be), but it should at least fix the reported error without introducing new failures. See additional notes in #34509. |
I only fixed a small test, the credits goes to @SamWheating |
* Improve stability of remove_task_decorator function * fix statics * test * remove test --------- Co-authored-by: Sam Wheating <[email protected]> (cherry picked from commit f1301da)
* Improve stability of remove_task_decorator function * fix statics * test * remove test --------- Co-authored-by: Sam Wheating <[email protected]> (cherry picked from commit f1301da)
closes: #34154
cc: @SamWheating
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rst
or{issue_number}.significant.rst
, in newsfragments.