You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ryan.berg: question on dask-kubernetes, I get a ERROR - prefect.FlowRunner | Unexpected error: ValueError(“Unexpected keyword arguments: [‘processes’, ‘silence_logs’]“,)
Traceback (most recent call last):
File “/usr/local/lib/python3.6/dist-packages/prefect/engine/runner.py”, line 48, in inner
new_state = method(self, state, *args, **kwargs)
File “/usr/local/lib/python3.6/dist-packages/prefect/engine/flow_runner.py”, line 393, in get_flow_run_state
with executor.start():
File “/usr/lib/python3.6/contextlib.py”, line 81, in enter
return next(self.gen)
File “/usr/local/lib/python3.6/dist-packages/prefect/engine/executors/dask.py”, line 74, in start
self.address, processes=self.local_processes, **self.kwargs
File “/usr/local/lib/python3.6/dist-packages/distributed/client.py”, line 651, in init
“Unexpected keyword arguments: {}“.format(str(sorted(kwargs)))
ValueError: Unexpected keyword arguments: [‘processes’, ‘silence_logs’] when trying to connect to a local dask scheduler created using KubeCluster()
chris: Hmmm those are keyword arguments we use for the standard dask client that makes the connection - can you confirm you are using the most recent version of distributed?
ryan.berg: I was using dask[complete]==2.6.0 tried 2.5.2 now trying 2.7.0
ryan.berg: <@UKNSNMUE6> I noticed dask/distributed#3151 wasn’t sure if this is related, why I went back to 2.5.2
chris: Yea I believe we fixed that on the prefect side - are you using 0.7.1?
ryan.berg: nope, 0.6.6 I will give that a go thx
chris: Ah great yea I suspect that will resolve the issue :hand_with_index_and_middle_fingers_crossed:
Archived from the Prefect Public Slack Community
ryan.berg: question on dask-kubernetes, I get a ERROR - prefect.FlowRunner | Unexpected error: ValueError(“Unexpected keyword arguments: [‘processes’, ‘silence_logs’]“,)
Traceback (most recent call last):
File “/usr/local/lib/python3.6/dist-packages/prefect/engine/runner.py”, line 48, in inner
new_state = method(self, state, *args, **kwargs)
File “/usr/local/lib/python3.6/dist-packages/prefect/engine/flow_runner.py”, line 393, in get_flow_run_state
with executor.start():
File “/usr/lib/python3.6/contextlib.py”, line 81, in enter
return next(self.gen)
File “/usr/local/lib/python3.6/dist-packages/prefect/engine/executors/dask.py”, line 74, in start
self.address, processes=self.local_processes, **self.kwargs
File “/usr/local/lib/python3.6/dist-packages/distributed/client.py”, line 651, in init
“Unexpected keyword arguments: {}“.format(str(sorted(kwargs)))
ValueError: Unexpected keyword arguments: [‘processes’, ‘silence_logs’] when trying to connect to a local dask scheduler created using KubeCluster()
chris: Hmmm those are keyword arguments we use for the standard dask client that makes the connection - can you confirm you are using the most recent version of distributed?
ryan.berg: I was using dask[complete]==2.6.0 tried 2.5.2 now trying 2.7.0
ryan.berg: <@UKNSNMUE6> I noticed dask/distributed#3151 wasn’t sure if this is related, why I went back to 2.5.2
chris: Yea I believe we fixed that on the prefect side - are you using 0.7.1?
ryan.berg: nope, 0.6.6 I will give that a go thx
chris: Ah great yea I suspect that will resolve the issue :hand_with_index_and_middle_fingers_crossed:
josh: <@ULVA73B9P> archive “dask-kubernetes unexpected keyword arguments”
The text was updated successfully, but these errors were encountered: