feat: run health checks and stall timeout for workflow runs#8
Merged
Conversation
Signed-off-by: Ibrahim Kazimov <74775400+ibrahimkzmv@users.noreply.github.com>
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.
What
Adds run health assessment so Forge does not treat hung or empty runs as successful completions. A stall watchdog fails runs with no workflow activity for a configurable window (default 5 minutes). Completion checks flag success-without-output and subprocess exits without a
resultevent. Snapshots and the UI exposehealthwith issue codes and messages.Why
For a debugging tool, a green "completed" state when the agent hung or produced nothing is misleading. This makes terminal run state trustworthy and gives operators a clear signal (stall, no result, empty output, task failures) instead of a silent false positive.
Checklist
npm run lintpassesnpm testpasses