Repository navigation
[Feat]: Improve server concurrency architecture #869
Description
Is your feature request related to a problem? Please describe.
The final goal of this effort is to relax or describe limitations on concurrency in AgentExecutor.
In existing version there is multiple hidden assumptions internally between classes as well as in API (e.g. AgentExecutor.cancel() can't wait for AgentExecutor.execute to finish).
Describe the solution you'd like
The plan is to make incremental changes on concurrency to ensure we can track down invalid change if new concurrency issue is introduced.
Describe alternatives you've considered
No response
Additional context
No response
Code of Conduct
- I agree to follow this project's Code of Conduct
Activity
feat: EventQueue - unify implementation between python versions (#877)
feat: InMemoryTaskStore creates a copy of Task by default to make it …
feat: Create EventQueue interface and make tap() async. (#914)
feat: Implementation of DefaultRequestHandlerV2 (#933)
feat: Unhandled exception in AgentExecutor marks task as failed (#943)
feat: EventQueue is now a simple interface with single enqueue_event …
feat: Support Message-only simplified execution without creating Task (…
feat: Simplify ActiveTask.subscribe() (#958)
feat: Support AgentExectuor enqueue of a Task object. (#960)
chore(1.0-dev): release 1.0.0-alpha.1 (#861)
docs: AgentExecutor interface documentation (#976)
feat!: Raise errors on invalid AgentExecutor behavior. (#979)
fix: compare in-memory task timestamps numerically (#1233)
test: install HTTP dependencies for the legacy cross-version server (#…