The `workdir` setting does not appear to work for the Dask/local executors

[Andrew-S-Rosen]

Environment

• Covalent version: 0.234.0rc0
• Python version: 3.10.13
• Operating system: Ubuntu

What is happening?

Back in #1619, the workdir setting was introduced for the Dask and local executors to allow for user-specified working directories. The default workdir is typically something like the following:

/home/rosen/.cache/covalent/workdir

which can be seen with a ct.get_config() check. One would expect, then, the files (by default) to be written out to this workdir directory, but they are not. The proof is shown below.

How can we reproduce the issue?

import covalent as ct

@ct.lattice
@ct.electron
def test():
    from pathlib import Path

    return Path.cwd()

ct.dispatch(test)()

In my case, I got back

/home/rosen/software/miniconda/envs/covalent/lib/python3.10/site-packages/covalent_ui

When I try changing doing

import covalent as ct

ct.set_config({"executors.dask.workdir": "/home/rosen/test"})

and rerunning the above script again, I still get the same answer back.

What should happen?

The working directory of the Python process when run via the Dask or local executors should correspond to the workdir variable.

Any suggestions?

No response