.Net Agents - Protect against null-reference for Assistant file-search result when streaming #9742
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.
Motivation and Context
Fixes: #9723
Must distinguish between file-search result and function-call result for assistant streaming without triggering
NullReferenceExceptionDescription
A file-search result provide any streaming result; rather, it results in an annotation on the assistant message. Still it must be distinguished from a function-call result.
Since
RunStepDetailsUpdate.FunctionNameproperty throws aNullReferenceExceptionwhen being evaluated, usingRunStepDetailsUpdate.FunctionResultproperty.Merged fix to Open AI SDK: openai/openai-dotnet#293
Contribution Checklist