(where '$opt' has a few parameters filled in, i.e. ChopGFF:CYTOBAND=...).

From the workbench page on 9tee4, I see the status of the pipeline template as 'not running', even though the pipeline is running (from the command line on my VM) and the relevant job from that pipeline is executing (and appears in workbench).

History

discuss with Peter and Tom: what's the desired behavior here? Should API server recognize the pipeline status as "running" if it is not being managed by crunch-dispatch, and if not, how do we communicate that to the user?

discuss with Peter and Tom: what's the desired behavior here? Should API server recognize the pipeline status as "running" if it is not being managed by crunch-dispatch, and if not, how do we communicate that to the user?

State should be RunningOnClient. Workbench should render as running, with some way to tell the difference between OnClient and OnServer. (Perhaps "Running" / "Running in user terminal session"?)

Subject changed from CLI 'arv pipeline run --run-pipeline-here' does not update the state from 'ready' (or 'not running'?) to 'run' to [SDKs] CLI 'arv pipeline run --run-pipeline-here' should change instance state from 'ready' (or 'not running'?) to 'RunningOnClient'