-
-
Notifications
You must be signed in to change notification settings - Fork 913
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
Kombu 4.2.0 breaks with celery 4.1.0 #873
Comments
Hi, I'm observing similar behaviour however freezing version numbers did not work for me. Even with kombu 4.1.0 and celery 4.1.0 I get same stack trace as posted by original poster. If I install celery 4.1.1 and kombu 4.2.0 then I get missing module error:
|
could you please use celery 4.1.1 or 4.2rc4 and let us know what error you got? |
|
Hi, in my case when I have seen this error I noticed a "kombu" folder was created in the root of my venv. In the same time I still could see kombu in venv-related site-packages. As soon as I removed this weird "kombu" from venv root everything worked fine for me. |
@auvipy Is it possible we made a mistake? See #873 (comment) |
let me check |
Omer, I checked locally land it works for me, not sure if they are working on production and didn't restart after updating? |
I can also confirm that removing the venv root's Perhaps there is something fishy during the installation of kombu? |
may be it's a local env cache issue? |
I tried uninstalling kombu and then My package is: I just started learning Celery today and ran into this problem. Feelsbad hahaa |
@auvipy I think that at this point we can consider this another blocker. |
what do you think could be the issue? |
I really don't know. I checked the spelling of the import and it looks fine. |
Omer I still thing this isn't a blocker since it's working fine locally on my machine, even with py3.7-dev, I guess local pycache of specific local env is causing this. but who knows? |
Hi, I found the problem in data_files in setup.py, it create a data folder for kumbo containing .pyc files for python 3.6 from one who build the wheel. i think he is @thedrow
to verify you could download the wheel from pypi and extract it to see the problem I install it in vrtualenv with python2.7, python3.6 and both fail to work. as I noted before I think there is problem in setup.py -> data_files |
thanks for digging it! |
Thanks! |
Hello, I have been trying to get my airflow (1.9.0) worker fixed and none of the solutions have worked. I continue to get this error after pinning celery to 4.1.0 and kombu to 4.1.0 Is there a version combination that does work?
|
Celery 4.2 and Kombu 4.2. |
I'll try those versions but I do not think we are using virtualenv. We are using Dockerfiles to build images and use those images to run everything in Kubernetes. Should we be using virtualenv? |
that version combination worked! thanks for the help |
…AttributeError: async when trying to run worker pods See celery/kombu#873 for more info
…AttributeError: async when trying to run worker pods See celery/kombu#873 for more info
…AttributeError: async when trying to run worker pods See celery/kombu#873 for more info
…AttributeError: async when trying to run worker pods See celery/kombu#873 for more info
…AttributeError: async when trying to run worker pods See celery/kombu#873 for more info
…AttributeError: async when trying to run worker pods See celery/kombu#873 for more info
…AttributeError: async when trying to run worker pods See celery/kombu#873 for more info
Hi,
I saw that yesterday kombu released version 4.2.0.
After this release celery 4.1.0 starts to break. I guess it should have a release with this change in celery too.
My solution was to force kombu 4.1.0 in my requirements.
The text was updated successfully, but these errors were encountered: