Allow concurrent runs in different workspaces
Track each active run's resolved workspace alongside its cancel function in a single runner.active struct map. A new request key is now refused only when an already-active run is changing the same resolved workspace; the refusal names the conflicting run id and advises waiting or using a different workspace. Workspace resolution is unchanged (default cwd, absolute request workspace, EvalSymlinks), so two spellings of one directory still compare equal. The conflict check and registration stay inside the existing r.mu critical section, so concurrent starts for one workspace cannot both pass. Idempotent repeats of an active request key and the restart-recovery guard are unchanged. Add concurrency_test.go covering concurrent different-workspace runs, same-workspace refusal, symlink/default-cwd equivalence, idempotent repeats, restart recovery and retry workspace scoping; strengthen the runner_test.go refusal assertion. Update docs/cli.md, docs/first-version-testing.md and the packaged operations skill reference to describe per-workspace concurrency. Assisted-by: DeepSeek V4.1 Flash
This commit is contained in:
@@ -95,7 +95,9 @@ delivery to your phone. A summary starter does not send alerts automatically.
|
||||
|
||||
## Known boundaries
|
||||
|
||||
- Sequential stages only; no parallel execution or built-in human-approval stages.
|
||||
- Sequential stages within a run; no parallel branches or built-in
|
||||
human-approval stages. Independent runs in different workspaces do execute
|
||||
concurrently.
|
||||
- Cancellation/retry is **not rollback**. Retry starts from the entry stage with
|
||||
fresh sessions and the pinned definition; earlier side effects can repeat.
|
||||
- Diffs are bounded stage-start/stage-end observations, not full backups or proof
|
||||
|
||||
Reference in New Issue
Block a user