You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 20e14bf
Browse filesBrowse the repository at this point in the historyBrowse files
fix(executor): honor stop-after over pending pauses and carry it on resume
Three changes for issue #8661:
1. The engine now lets stop-after win over a pause still pending on another
branch. Reaching the stop target completes the run and drops the pause
points instead of returning 'paused' and persisting a resume that can never
finish. (executor/execution/engine.ts)
2. stopAfterBlockId is rejected upfront when it targets a block that pauses
(human-in-the-loop or wait). Such a target cannot be honored: the run pauses
there and the resume path prunes its outgoing edges, so the stop target would
be lost. (executor/utils/stop-after.ts, execution-core.ts)
3. stopAfterBlockId is persisted in the pause snapshot and passed back into the
resumed run, so a run that pauses on another branch still ends after its
original stop target. (execution/types.ts, snapshot-serializer.ts,
human-in-the-loop-manager.ts)
Tests: an engine case for stop-after vs a pending pause, a serializer case for
the carried stop target, and unit coverage for the pausing-target check.
0 commit comments