-
Notifications
You must be signed in to change notification settings - Fork 801
Python: [Breaking] Python: Respond with AgentRunResponse with serialized structured output
#2285
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
Open
larohra
wants to merge
17
commits into
microsoft:main
Choose a base branch
from
larohra:fix-func-agent-response
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
17 commits
Select commit
Hold shift + click to select a range
53b6cc0
Respond with AgentRunResponse
larohra 262c6f5
Merge branch 'main' into fix-func-agent-response
larohra 92260d7
Fix response_Format type
larohra 47ef15f
Address comments
larohra 51b710d
Merge branch 'microsoft:main' into fix-func-agent-response
larohra 8d645c9
Merge branch 'main' into fix-func-agent-response
larohra 01495e3
Merge branch 'main' into fix-func-agent-response
larohra f3bfc8e
Fix tests
larohra cd07aab
Fix log
larohra 50dcf68
Merge branch 'main' into fix-func-agent-response
larohra cc504c5
Addressed comments
larohra 22cd334
Merge branch 'main' into fix-func-agent-response
larohra 2a0ca25
Merge branch 'main' into fix-func-agent-response
larohra 804b4bb
Merge branch 'main' into fix-func-agent-response
larohra 62f1b51
Merge branch 'main' into fix-func-agent-response
larohra 62a79de
Code cleanup
larohra fbff509
Merge branch 'main' into fix-func-agent-response
larohra File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Some comments aren't visible on the classic Files Changed page.
There are no files selected for viewing
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like you're creating a custom error response from the entity when something unexpected happens, but I don't believe we're doing this in .NET. I'm also not sure if this is the right thing for us to do since it hides the fact that an error occurred from Functions telemetry. Regardless of what design we think is best, we should do the same thing in both languages. Can you open an issue to review the implementation and track consistent error handling for agent invocations?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree, the experiences should be consistent.
Created an issue to track this separately - #2434