chore(chat): log full provider errors during chat turns#53
Merged
Conversation
The user-facing chat panel only sees the short `LLMError::to_string()` wrapper (e.g. "Error decoding response"), which strips the original HTTP status / body / decode path. Thread the session Logger and a `<backend>/<model>` tag through `ChatTurn` and log every: - stream-open retry failure (Display + Debug shape) - mid-stream error (with round + partial-text length) - tool dispatch drop - tool-budget overrun - turn start / done summary - build_client failure so post-mortem diagnosis from `.rowdy/<datetime>.log` is possible.
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
1 participant
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.
Summary
Chat errors like "Http Error: Error decoding response" surface to the user via the short `LLMError::to_string()` wrapper, which strips the original HTTP status, body, and decode path. Nothing was making it to the session log either, so failures were undebuggable after the fact.
This change threads the session `Logger` and a `/` provider tag through `ChatTurn`, then logs:
User-visible behaviour is unchanged; the new lines land in `.rowdy/.log` under target `chat`.
Test plan