Make chat participant/provider calls resilient; handle exceptions and… #286627
+119
−32
Conversation
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
Author
|
@microsoft-github-policy-service agree |
… return safe defaults (microsoft#286618)
sandorsett
force-pushed
the
fix/chat-provider-errors-286618
branch
from
b60ce14 to
2c0c91d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Fixes #286618
Summary:
Wrap calls to extension-provided chat APIs (title, summary, followups, participant detection) in try/catch so exceptions from providers do not bubble up and break the chat UI.
Log unexpected provider errors and return safe defaults (empty array or undefined) so chat flows remain functional.