-
Notifications
You must be signed in to change notification settings - Fork 57
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
Cannot create Dask Client to a dask-scheduler with UCX protocol #459
Comments
I tried reproducing with a clean env today and was unable. I believe @randerzander is assessing his conda env |
This corresponds to a change upstream. I suspect that not all of the
components of the Dask cluster have been fully updated to master.
…On Wed, Mar 18, 2020, 7:36 AM Benjamin Zaitlen ***@***.***> wrote:
I tried reproducing with a clean env today and was unable. I believe
@randerzander <https://github.com/randerzander> is assessing his conda env
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#459 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACKZTD5GFEC6JKTPW7MNLDRIDL5FANCNFSM4LOSR6TQ>
.
|
Resolved after rebuilding environments. Thanks! |
FYI @jrbourbeau
…On Wed, Mar 18, 2020 at 10:14 AM Randy Gelhausen ***@***.***> wrote:
Closed #459 <#459>.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#459 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACKZTFV4JAZRSXFZVVRND3RID6QXANCNFSM4LOSR6TQ>
.
|
What change are you referring to Matt? 🙂 |
We added the Python version to the list of version checks in dask/distributed#3567. I suspect |
With latest nightlies:
I'm no longer able to create a Dask Client object to a scheduler running with UCX protocol:
The scheduler was started as:
The text was updated successfully, but these errors were encountered: