feat: add timeout field to RemoteTool#118
Conversation
|
Thank you for your pull request and welcome to our community! To contribute, please sign the Oracle Contributor Agreement (OCA).
To sign the OCA, please create an Oracle account and sign the OCA in Oracle's Contributor Agreement Application. When signing the OCA, please provide your GitHub username. After signing the OCA and getting an OCA approval from Oracle, this PR will be automatically updated. If you are an Oracle employee, please make sure that you are a member of the main Oracle GitHub organization, and your membership in this organization is public. |
oracle-contributor-agreement
bot
added
the
OCA Required
Add an optional `timeout` field to `RemoteTool` that is forwarded
directly to `httpx.request()`. This allows agent spec authors to
configure per-tool HTTP timeouts for slow endpoints such as
transcription or inference services.
The field defaults to `None`, preserving existing behaviour where
httpx uses its own default timeout (5 seconds).
Example usage in an agent spec:
{
"component_type": "RemoteTool",
"timeout": 300.0,
...
}
MAabdelmoumen
force-pushed
the
feat/remote-tool-timeout
branch
from
10ddeae to
2a69050
Compare
|
Hi @MAabdelmoumen , We were actually designing internally some new field in components that do remote operations to be able to configure a retry-policy. That retry-policy would make it possible to configure a timeout. cc @sonleoracle |
2 participants
Add an optional
timeoutfield toRemoteToolthat is forwarded directly tohttpx.request(). This allows agent spec authors to configure per-tool HTTP timeouts for slow endpoints such as transcription or inference services.The field defaults to
None, preserving existing behaviour where httpx uses its own default timeout (5 seconds).Example usage in an agent spec:
{
"component_type": "RemoteTool",
"timeout": 300.0,
...
}