Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

.Net: Function Calling Planner: Catch exceptions and output error messages to chat history #4455

Merged
merged 5 commits into from
Jan 3, 2024

Conversation

gitri-ms
Copy link
Contributor

@gitri-ms gitri-ms commented Jan 2, 2024

Motivation and Context

Resolves #3224. Exceptions thrown by invoked functions are currently not being caught by the planner.

Description

This change catches any non-critical exceptions from function invocation, adds the error message into chat history, and lets the planner retry.

Contribution Checklist

Sorry, something went wrong.

@gitri-ms gitri-ms requested a review from a team as a code owner January 2, 2024 21:05
@shawncal shawncal added the .NET Issue or Pull requests regarding .NET code label Jan 2, 2024
@github-actions github-actions bot changed the title Function Calling Planner: Catch exceptions and output error messages to chat history .Net: Function Calling Planner: Catch exceptions and output error messages to chat history Jan 2, 2024
@gitri-ms gitri-ms self-assigned this Jan 2, 2024
@gitri-ms gitri-ms added the PR: in progress Under development and/or addressing feedback label Jan 2, 2024
@shawncal shawncal added the kernel Issues or pull requests impacting the core kernel label Jan 2, 2024
@gitri-ms gitri-ms added PR: ready for review All feedback addressed, ready for reviews and removed PR: in progress Under development and/or addressing feedback labels Jan 3, 2024
@gitri-ms gitri-ms requested a review from alliscode January 3, 2024 17:54
@gitri-ms gitri-ms added this pull request to the merge queue Jan 3, 2024
Merged via the queue into microsoft:main with commit aa62b14 Jan 3, 2024
@gitri-ms gitri-ms deleted the fc-planner-catch-exceptions branch January 3, 2024 22:43
Bryan-Roe pushed a commit to Bryan-Roe-ai/semantic-kernel that referenced this pull request Oct 6, 2024
…sages to chat history (microsoft#4455)

### Motivation and Context

<!-- Thank you for your contribution to the semantic-kernel repo!
Please help reviewers and future users, providing the following
information:
  1. Why is this change required?
  2. What problem does it solve?
  3. What scenario does it contribute to?
  4. If it fixes an open issue, please link to the issue here.
-->
Resolves microsoft#3224. Exceptions thrown by invoked functions are currently not
being caught by the planner.

### Description

<!-- Describe your changes, the overall approach, the underlying design.
These notes will help understanding how your code works. Thanks! -->
This change catches any non-critical exceptions from function
invocation, adds the error message into chat history, and lets the
planner retry.

### Contribution Checklist

<!-- Before submitting this PR, please make sure: -->

- [x] The code builds clean without any errors or warnings
- [x] The PR follows the [SK Contribution
Guidelines](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md)
and the [pre-submission formatting
script](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md#development-scripts)
raises no violations
- [x] All unit tests pass, and I have added new tests where possible
- [x] I didn't break anyone 😄
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kernel Issues or pull requests impacting the core kernel .NET Issue or Pull requests regarding .NET code PR: ready for review All feedback addressed, ready for reviews
Projects
None yet
Development

Successfully merging this pull request may close these issues.

.Net: How to output error messages to [OBSERVATION] in native functions
4 participants