feat(web): show detailed diagnostics for model request failures - #1756
Merged
Conversation
Surface the coded provider error the daemon already sends: a semantic title per error code, the provider's raw message, and expandable diagnostics (error code, HTTP status, request ID, SDK error name) with copy support, instead of a bare text-only toast.
🦋 Changeset detectedLatest commit: 845a591 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
commit: |
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.
Related Issue
No linked issue — the problem is explained below.
Problem
When a model endpoint call fails in the web UI (rate limit, invalid API key, unreachable endpoint, model not found), the only feedback was a bare text toast such as
错误: Connection error.— no error code, no HTTP status, no request ID, and the raw provider response was truncated into a single line that auto-dismisses after 12 seconds. The daemon already sends the full coded error payload (code,message,details.statusCode,details.requestId,retryable) on the wire, but the web client discarded everything except the message string, so users had nothing actionable for troubleshooting.What changed
agentEventProjectornow passes the full error payload through (name/details/retryable) instead of keeping onlycode+message.eventReducerbuilds a structuredAppNoticefor agent errors: a semantic title mapped from the error code (rate limit / auth / overloaded / connection / filtered / context overflow / generic), the provider's raw message as the body, and a diagnostics list (error code, HTTP status, request ID, SDK error name, plus any extra detail fields such asfinishReason).WarningToastsdetails/copy UI ("Show details" / "Copy diagnostics") — no new component; en/zh i18n keys added underwarnings.agentError.Checklist
gen-changesetsskill, or this PR needs no changeset.gen-docsskill, or this PR needs no doc update.