-
-
Notifications
You must be signed in to change notification settings - Fork 108
Closed
Labels
AgentIssues & PRs about the AI Agent componentIssues & PRs about the AI Agent componentPlatformIssues & PRs about the AI Platform componentIssues & PRs about the AI Platform componentRFCRFC = Request For Comments (proposals about features that you want to be discussed)RFC = Request For Comments (proposals about features that you want to be discussed)
Description
Currently there is two call to serializer
- one in ToolResultConverter
return $this->serializer->serialize($result, 'json'); - one in AgentProcessor
$this->serializer->deserialize($output->getResult()->getContent(), $this->outputStructure, 'json')
One issue is the fact,
- Those call might throw exception (I recently got a MissingConstructorArgumentsException because the AI call didn't return the expected format of data)
- Those exception are not documented anywhere
- ToolResultConverter::convert has no throws tag, so does
Toolbox\AgentProcessor::processOutput - AgentProcessor::processOutput has no throws tag
- ToolResultConverter::convert has no throws tag, so does
What could be interesting if you agree with @chr-hertel @OskarStark would be
- To try/catch those call in order to throw an exception from symfony/agent
- To document the
processOutputthat such exception could be thrown
Basically InputProcessorInterface::processInput and OutputProcessorInterface::processOutput should be restricted to throws Symfony\AI\Agent\Exception\ExceptionInterface only.
Metadata
Metadata
Assignees
Labels
AgentIssues & PRs about the AI Agent componentIssues & PRs about the AI Agent componentPlatformIssues & PRs about the AI Platform componentIssues & PRs about the AI Platform componentRFCRFC = Request For Comments (proposals about features that you want to be discussed)RFC = Request For Comments (proposals about features that you want to be discussed)