Repository navigation
Record the step a run is executing on its record, cleared when the step ends (1.8.0) - #64
Merged
Merged
Conversation
…ep ends (1.8.0) The trace gains an entry only when a step ends, so a running flow showed nothing about what it was doing. The run record now carries running: the step's name and type, when it started, its per-attempt timeout, and for an agent step the resolved session it runs in. Each exit from a step clears it in the same write that records the step's end.
…ing-step # Conflicts: # package-lock.json # package.json # tests/core.test.ts
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.
Why
A run's trace gains an entry only when a step ends. While a step runs, a reader of the run record sees
status: "running"and nothing about what the run is doing, how long the step has taken, or what it is waiting on. An agent step that waits for a busy session looks the same as one making progress.What changes
runningwhile a top-level step executes: the step's name and type, when it started, its per-attempt timeout, and for an agent step the resolved session it runs in (agent,sessionKey,sessionId, after template interpolation).RunningStep.Sub-flows (loop iterations, branches) record their own running step in their own records; the parent shows the loop or branch step itself.
Checks
npm test: 249 of 249 pass, 2 of them new (recorded while running with the resolved session, cleared after success and after failure). The tests stub theopenclawCLI.tsc --noEmitis clean.This branch is independent of #63; both bump the version, so whichever merges second takes the higher one.