Repository navigation
fix(server): a run restarted after its checkpoint no longer stays waiting - #150
Merged
Merged
Conversation
A steer can read a run as running, and the run can then finish and capture its checkpoint before the steer commits its restart. The restarted attempt must still complete the run. Today the run stays waiting. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ting The checkpoint capture used the run id twice as its dedupe key: as the outbox effect id and as the command id of the capture's commit. When a late steer restarted a run that had already captured, the restarted attempt's capture was dropped at both points, so nothing moved the run from waiting to completed and every later message queued behind it. Key the effect id and the commit command id by run attempt. The outbox command id stays per run, so startup recovery still finds every attempt's capture, including rows written before this change. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Thread transfer impact✅ Thread transfer remains within every enforced ceiling.
Other scenariosAll 64 scenario measurements match All 64 scenario measurements
Baseline: Scenario and decoded snapshot size10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.
Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request stops a thread from hanging in "waiting" after a steer restarts a turn that had already finished.
改了什么行为
Behaviour change: no. A run whose restarted turn ends now completes, and the thread's queued messages start again.
Cause and fix
If a turn finishes while a steer is restarting it, the run is checkpointed first and then restarted. The checkpoint capture used the run id as its outbox effect id and as the command id of its commit, so the restarted attempt's capture was dropped at both points and the run never left "waiting".
Both ids now name the run attempt. The outbox command id stays per run, so startup recovery still finds every attempt's capture, old rows included.
Verification
SteeringCompletion.integration.test.tsholds the steer after it reads the run, ends the turn, then ends the restarted turn, once completed and once interrupted. Both fail on the first commit and pass on the second.vp run check:changedpasses.Details and scope