zachliu commented on PR #49747:
URL: https://github.com/apache/airflow/pull/49747#issuecomment-2874825490

   > Yes new provider wave is coming - but if you want you can easily (now) 
build provider on your own from main and test it - or even install it via 
github URL:
   > 
   > ```
   > pip install "apache-airflow-providers-celery @ 
git+https://github.com/apache/airflow/#subdirectory=providers/celery";
   > ```
   
   This journey from Airflow 2 to 3 has made me reluctant to be the first to 
"eat the crab" again. And I hate being proven right once more… after building 
and installing the latest Celery provider from main, I'm still getting 
bombarded with `ConnectError: [Errno 111] Connection refused` if I don't set 
the `AIRFLOW__CORE__EXECUTION_API_SERVER_URL` environment variable somewhere.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to