-
Notifications
You must be signed in to change notification settings - Fork 14.7k
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
Context deprecation warnings when they aren't used #20213
Comments
38 tasks
We are unpacking the context too eagerly. The rendering functions need to use a much lower level Jinja2 interface. |
Merged
Warnings are also present in
|
Thanks for spotting it, I’ll add the fix to the PR as well. |
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Apache Airflow version
2.2.3rc1 (release candidate)
What happened
I ran a DAG that does nothing explicitly with context, so I'm surprised to see deprecation warnings about context being used (trimmed to cut down on noise):
What you expected to happen
I'd only expect to see deprecation warnings about things my DAG is actually interacting with.
How to reproduce
Run this DAG:
Note: I also tried a TaskFlow DAG and that wasn't impacted.
Operating System
MacOS 11.6
Versions of Apache Airflow Providers
No response
Deployment
Virtualenv installation
Deployment details
No response
Anything else
This was introduced in #19886 (cc @uranusjr).
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: