Skip to content
Discussion options

You must be logged in to vote

That warning comes from Uvicorn, not from an Airflow setting directly. It means Uvicorn was given something that looks like an ASGI application factory, so it can still run it, but it warns because you would normally pass the equivalent factory option explicitly when starting Uvicorn. In this case, since the triggerer or scheduler start that internal server themselves, there probably is not an airflow.cfg option you can set manually for this. If everything is working, I would treat it as a harmless warning rather than something you need to fix locally. The Airflow-side fix would likely be for the code path that starts Uvicorn to pass the factory option explicitly so Uvicorn does not warn.…

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by static-moonlight
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants