feat: improve error messaging for stream termination errors from provider #10548
+38
−19
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
When the backend provider (Roo Code Cloud) terminates a stream prematurely, users previously saw raw error messages like "terminated" without context. This made it unclear that the error came from the provider, not the extension itself.
Changes
streamTerminatedByProviderinsrc/i18n/locales/en/common.jsonsrc/core/task/Task.tsto use the new i18n key when formatting stream termination errorsMessage Translations
Before
Users saw raw error like:
terminatedAfter
Users see:
Provider ended the request: terminatedImpact
Users will now understand when errors are caused by the backend provider (timeouts, rate limits, backend issues) rather than the extension itself.
Closes ROO-415