James Bourbeau

Good point -- that would also keep things lazy. The main downside I can think of is if we return a `Delayed` we would loose all the array-specific optimizations (e.g....

Thanks for the extra context @jsignell. I'm happy raising a very informative error in these cases > Geraldine and I are watching this thread to see how it turns out...

No worries @dustinwerran2, I totally understand. Unfortunately I'm not aware of a quick fix at the moment

Thanks for raising this issue @LUOXIAO92. It's not clear to me if this is a `dask/dask` issue or a `dask/dask-mpi` issue. Could you post logs / tracebacks? A message like...

Just checking in here -- I wouldn't want to add a lot of infrastructure to support this (unless more folks show up asking for this). That said, I'm not sure...

Thanks for reporting @lukeconibear

Here's an example of what this might look like for `p2p` ```diff diff --git a/dask/core.py b/dask/core.py index 751f8f345..bfeffce04 100644 --- a/dask/core.py +++ b/dask/core.py @@ -532,3 +532,6 @@ def quote(x): if...

Hrm, while I agree the examples @ncclementi are totally correct. One thing I noticed when playing around with the environment variable approach is that `DASK_DISTRIBUTED__WORKER__RESOURCES__MEMORY=32` sets a resource of `memory=32`...

> Do you mean `job = dask_client.submit(some_task, resources={'memory': 20})` Yeah, exactly. Resources are set when we create the worker with this environment variable ``` DASK_DISTRIBUTED__WORKER__RESOURCES__MEMORY=32 dask-worker ``` and then with...

Hrm, that's a weird one. Thanks for reporting @ncclementi. I'm also not immediately able to reproduce locally, so will need to dig in a bit more. EDIT: it seems extra...