fix(ai): remove error logging in sendMessageStream()
#9352
Closed
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.
Removes error logging in
sendMessageStream(). These errors are catchable by the user, so there is no need to log them. This removes the anti-pattern of throwing aSILENT_ERRORto skip promise chains.This fix is important for when we add AbortSignal. Since aborting a request raises an
AbortError, every time a request is aborted, there will be an error logged to the console, which is undesirable for the user.