When I try to call a task like the add task from the documentation I get the following traceback.
Traceback (most recent call last):
File "/Users/michael/.virtualenvs/wavcrate2/lib/python2.7/site-packages/celery/app/trace.py", line 283, in trace_task
uuid, retval, SUCCESS, request=task_request,
File "/Users/michael/.virtualenvs/wavcrate2/lib/python2.7/site-packages/celery/backends/base.py", line 257, in store_result
request=request, **kwargs)
File "/Users/michael/.virtualenvs/wavcrate2/lib/python2.7/site-packages/celery/backends/base.py", line 491, in _store_result
self.set(self.get_key_for_task(task_id), self.encode(meta))
File "/Users/michael/.virtualenvs/wavcrate2/lib/python2.7/site-packages/celery/backends/redis.py", line 160, in set
return self.ensure(self._set, (key, value), **retry_policy)
File "/Users/michael/.virtualenvs/wavcrate2/lib/python2.7/site-packages/celery/backends/redis.py", line 149, in ensure
**retry_policy
File "/Users/michael/.virtualenvs/wavcrate2/lib/python2.7/site-packages/kombu/utils/__init__.py", line 243, in retry_over_time
return fun(*args, **kwargs)
File "/Users/michael/.virtualenvs/wavcrate2/lib/python2.7/site-packages/celery/backends/redis.py", line 169, in _set
pipe.execute()
File "/Users/michael/.virtualenvs/wavcrate2/lib/python2.7/site-packages/redis/client.py", line 2572, in execute
self.shard_hint)
File "/Users/michael/.virtualenvs/wavcrate2/lib/python2.7/site-packages/redis/connection.py", line 874, in get_connection
connection = self.make_connection()
File "/Users/michael/.virtualenvs/wavcrate2/lib/python2.7/site-packages/redis/connection.py", line 883, in make_connection
return self.connection_class(**self.connection_kwargs)
TypeError: __init__() got an unexpected keyword argument 'socket_connect_timeout'
This just started happening when I upgraded to 3.1.19 from 3.1.18. The issue is fixed if I rollback to 3.1.18.
When I try to call a task like the add task from the documentation I get the following traceback.
This just started happening when I upgraded to 3.1.19 from 3.1.18. The issue is fixed if I rollback to 3.1.18.