Closed cpursley closed 3 months ago
Ah, yes, I can see it might. Some tools may do RAG lookups, query web pages, etc. A configurable timeout makes sense. What were you thinking? It could be an option on the run
. It could be a library config option. And regardless, it should probably default to a higher timeout that the default 5 seconds!
I'm leaning towards opt in run
In v0.3.0-rc.0, I added an explicit timeout of 2 minutes. That should get you past the immediate issue, but I agree that timeout control would be nice.
I'm experiencing this frequency:
Can we make the Task.await_many timeout configurable (either via config or pass as an optional arg in the run call)? Glad to submit a PR.