Repository navigation
hermes plugin: log why the routing frame or stall guard stayed idle - #304
Merged
Merged
Conversation
On 2026-11-07 the guard never fired on a live Winston turn although it fires in-process; these log lines show which id or platform did not match. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MrfsFu7NLgapPn6yUcNxE5
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.
On a live Winston turn on 2026-11-07, the stall guard never fired, even though it fires when called in-process in the same pod. This adds INFO log lines that record why the routing frame was skipped or why the guard stayed idle: platform, session id and turn id. That shows which id didn't match. Plugin tests: 105 passed.
🤖 Generated with Claude Code
https://claude.ai/code/session_01MrfsFu7NLgapPn6yUcNxE5