thedrow on master
Added integration test: test_al… (compare)
django-celery-beatproject was 20 days ago. I'm specially interested in a couple of pull requests so I was wondering myself how bussy are you to check them out
a_chord.id? I tried instantiating AsyncResult and GroupResult but no success
app.control.ping()mechanism. A couple of minutes ago I discovered that somehow our web worker would get an empty reply
, and when I opened a python prompt and called app.control.ping(), the expected pong was there. is there a way I can make sure there's a viable connection from my web worker process?
https:and the config clearly has
redis:second; 0.0.0.0 isn't a valid address to connect to, 0.0.0.0 tell a service to listen on all available addresses
Hey team, I had a question about building the celery code using docker-compose locally. I keep getting version conflicts while building the container.
The user requested kombu 5.3.0a1 (from git+https://github.com/celery/kombu.git) The user requested kombu 5.3.0a1 (from git+https://github.com/celery/kombu.git) The user requested kombu 5.3.0a1 (from git+https://github.com/celery/kombu.git) celery 4.4.0 depends on kombu<4.7 and >=4.6.7 To fix this you could try to: 1. loosen the range of package versions you've specified 2. remove package versions to allow pip attempt to solve the dependency conflict All I'm doing is building the container using `docker-compose build celery`. Could someone tell me what I might be doing wrong?
Also, if this is the wrong area to ask, I apologize in advance. Please point me to the right platform for my question