You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2020/06/09 16:05:40 UTC

[GitHub] [airflow] dinigo opened a new issue #9193: Celery 4.4.4 (known bug) lacks "future" module thus breaks airflow

dinigo opened a new issue #9193:
URL: https://github.com/apache/airflow/issues/9193


   Hello. We are experiencing some issues in local development due to a celery using a module that it doesn't install anymore.
   
   This happened when upping dependency version of celery 4.4.3 to 4.4.4
   
   **Apache Airflow version**: 2.0 - Official docker image (apache/airflow:master)
   
   **What happened**:
   
   Commit https://github.com/apache/airflow/commit/aa8990031d15b5c5b66fd9fb4b483d938e656bde updated celery 4.4.3 to 4.4.4  with the bug reported in here https://github.com/celery/celery/issues/6145. Celery 4.4.4 depends on future but doesn't require it.
   
   All of our local environments are failing
   
   **What you expected to happen**:
   Restore celery=4.4.3 in the requirements files and rebuild the dockerhub images
   
   **How to reproduce it**:
   Start the image normally
   
   **Anything else we need to know**:
   ![MicrosoftTeams-image](https://user-images.githubusercontent.com/3038962/84142004-5cda3300-aa54-11ea-99d3-7ead1687a5e9.png)
   


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [airflow] potiuk closed issue #9193: Breaks production Docker image: Celery 4.4.4 (known bug) lacks "future" module thus breaks airflow

Posted by GitBox <gi...@apache.org>.
potiuk closed issue #9193:
URL: https://github.com/apache/airflow/issues/9193


   


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [airflow] potiuk commented on issue #9193: Breaks production Docker image: Celery 4.4.4 (known bug) lacks "future" module thus breaks airflow

Posted by GitBox <gi...@apache.org>.
potiuk commented on issue #9193:
URL: https://github.com/apache/airflow/issues/9193#issuecomment-642175919


   Glad it helped :)


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [airflow] potiuk commented on issue #9193: Breaks production Docker image: Celery 4.4.4 (known bug) lacks "future" module thus breaks airflow

Posted by GitBox <gi...@apache.org>.
potiuk commented on issue #9193:
URL: https://github.com/apache/airflow/issues/9193#issuecomment-641502284


   Fixed in #9194 - the images should rebuild tonight (we have nightly builds) and they should contain celery 4.4.5 


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [airflow] dinigo commented on issue #9193: Breaks production Docker image: Celery 4.4.4 (known bug) lacks "future" module thus breaks airflow

Posted by GitBox <gi...@apache.org>.
dinigo commented on issue #9193:
URL: https://github.com/apache/airflow/issues/9193#issuecomment-641821549


   Thanks a lot @potiuk and @mik-laj! You saved my day :)


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org