Here's the full traceback

  File "/Users/davidg/Projects/buzz/bumlo/buzz_ml/training_pipeline.py", line 85, in <module>
    pipe.start_locally(run_pipeline_steps_locally=True)
  File "/Users/davidg/opt/anaconda3/envs/bumlo/lib/python3.10/site-packages/clearml/automation/controller.py", line 985, in start_locally
    self._start(wait=True)
  File "/Users/davidg/opt/anaconda3/envs/bumlo/lib/python3.10/site-packages/clearml/automation/controller.py", line 1590, in _start
    self._prepare_...

yup, @<1523701205467926528:profile|AgitatedDove14> that's exactly what I see as well ^

@<1523701070390366208:profile|CostlyOstrich36> I will try using a full path. hmm, any reason i'm not running in docker mode.... I suppose because I'm new to the platform and don't know how yet? Do you recommend that I make the switch?

OK we found the source of the error @<1523701070390366208:profile|CostlyOstrich36> :

It's quite strange. Apparently, using the string "ON" as a key in the PipelineController's config, and connecting it via

pipeline.connect_configuration(config)

results in that key being processed as a boolean. so for example if we define

config = {
"ON": False,
"param1": True,
...
}

we end with that config defined inside the pipeline object like so

{
True: False,
"param1": True,...

yes, specifically i'm following this: None

I'm getting lot of bizarre errors running without a docker image attached (still haven't gotten through all the issues in docker but i'm getting a lot further). For example, running the exact same pipeline in docker mode completes the first step fine but without docker i'm getting this:
virtualenv: error: argument dest: the destination . is not write-able at /hom...