Hi @<1627478122452488192:profile|AdorableDeer85> might you have been able to resolve this? I also gave the same challenge with remote execution
Hi @<1627478122452488192:profile|AdorableDeer85> , can you provide a code snippet that reproduces this?
What happens if you remove the run_locally() ?
And just making sure - the first pipeline step isn't even pushed into a queue? It remains in 'draft' mode?
Hi @<1523701070390366208:profile|CostlyOstrich36> , sorry for my late reply.
My description was not clear enough, what I mean is:
- I run a pipeline with
run_locally(). This can be any pipeline e.g. the example pipelines like this one None . The pipeline completes. - Then I open the successfully run pipeline in the UI and rerun it in a queue. The queue is observed by agents running in docker mode.
- The overall pipeline is "taken out" of the queue and shown as running on the worker. BUT then the pipeline execution does not proceed. I see the first pipeline component (that is the first single step) being enqueued as the next experiment to come but it is never dequeued and never started.