Xinzijian Liu

> @zjgemi Hello, what is your use case for these artifacts in this scope? In my case I have a conditional step. If the step is not skipped, the next...

[Ray](https://docs.ray.io/en/latest) is a pure-Python distributed compute framework. After a [ray cluster](https://docs.ray.io/en/latest/cluster/quickstart.html) set up, dflow steps or tasks can be assigned to run on the ray cluster as [remote functions](https://docs.ray.io/en/latest/ray-core/tasks.html#) or...

Add a syntactic sugar for recursion.

Another possible solution is using [executor plugins of Argo](https://argoproj.github.io/argo-workflows/executor_plugins/) to write an executor for Bohrium tasks. It is needed to develop a server which implements APIs to submit Bohrium jobs...

Are your Argo components installed in the `test` namespace as well? Because Argo will attempt to look for memoized configmaps in the same namespace by default.

https://argo-workflows.readthedocs.io/en/latest/managed-namespace/ If you only run workflows that are maintained by the same team that manages the Argo Workflows installation, you may want a namespace install (install all Argo components in...

SlurmRemoteExecutor has not been maintained for a while. Can you try to use DispatcherExecutor instead of SlurmRemoteExecutor? E.g. ```python from dflow.plugins.dispatcher import DispatcherExecutor dispatcher_executor = DispatcherExecutor( host= "xxx.xx.xxx.xx", port= xxx,...

Make sure the remote root (default: `/home/{username}/dflow/workflows`) exists on the remote cluster. The remote root can be specified as an argument of DispatcherExecutor.

> Are there any technical plans for UI, such as development based on Argo UI or just using Argo's API, even Kubernetes API to make a completely new one. Perhaps...