You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not sure if this one is a bug or by design or just functionality not there yet in SK.
I am trying to use a custom KernelFunctionSelectionStrategy and bumping up against an assertion error related to assert isinstance(self.items[0], FunctionResultContent)
It seems that SK is expecting assistant messages to only be function call results (rather than text content).
The context is I have an orchestration kernel with an AzureChatCompletion service. I'm creating a KernelFunctionFromPrompt that contains the custom selection strategy for multiple AzureAssistantAgents.
The first 2 turns of the selection strategy work as expected, but then I run into this assertion error. Any help or guidance with custom selection strategies would be appreciated. Or if this is a bug or missing functionality, I will stop banging my head against the wall trying to make it work.
The text was updated successfully, but these errors were encountered:
Not sure if this one is a bug or by design or just functionality not there yet in SK.
I am trying to use a custom
KernelFunctionSelectionStrategy
and bumping up against an assertion error related toassert isinstance(self.items[0], FunctionResultContent)
It seems that SK is expecting assistant messages to only be function call results (rather than text content).
The context is I have an orchestration kernel with an AzureChatCompletion service. I'm creating a
KernelFunctionFromPrompt
that contains the custom selection strategy for multipleAzureAssistantAgent
s.The first 2 turns of the selection strategy work as expected, but then I run into this assertion error. Any help or guidance with custom selection strategies would be appreciated. Or if this is a bug or missing functionality, I will stop banging my head against the wall trying to make it work.
The text was updated successfully, but these errors were encountered: