Log the response text if available when exception is thrown while processing a user query #338
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
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.
PR Summary
When an exception is thrown while processing a user query, we log the exception and the response text if it's available.
This can help us diagnose the exception. The response text is logged to the local log, not sent to the telemetry, so there is no privacy issue.
This PR also reset
_copilotResponseand the placeholder data when/refreshor when the user sends a new query, so that old data doesn't interfere when user runs/replaceafter/refresh, or when user runs/replaceafter it fails to get a response from Azure Copilot.