run-llama / llama-agents / 32578266738

85%

Build Type

push

github

Committed by web-flow

Commit Message

Reject concurrent reuse of active handler IDs (#738)

## Summary

- reject HTTP workflow starts that reuse a currently active handler ID
- return `409 Conflict` with a stable, actionable error from both
blocking and non-blocking run endpoints
- keep terminal handler ID reuse intact for existing state-handoff
workflows
- add endpoint regression coverage and a patch changeset for
`llama-agents-server`

## Validation

- `uv run pytest packages/llama-agents-server/tests -n0` (447 passed, 32
deselected)
- `uv run pytest packages/llama-agents-appserver/tests -n0` (107 passed)
- `uv run ruff format --check
packages/llama-agents-server/src/llama_agents/server
packages/llama-agents-server/tests/server`
- `uv run ruff check
packages/llama-agents-server/src/llama_agents/server
packages/llama-agents-server/tests/server`
- `uv run ty check
packages/llama-agents-server/src/llama_agents/server/_service.py
packages/llama-agents-server/src/llama_agents/server/_api.py
packages/llama-agents-server/tests/server/test_server_endpoints.py`
- `git diff --check origin/main...HEAD`

## Known gaps

The store lookup and handler creation are not a cross-process
compare-and-set operation. This change closes the existing HTTP service
path mismatch and does not claim distributed atomicity.

The full-repository pre-commit run could not complete locally because
the workspace environment does not include optional AgentCore, Control
Plane, and llamactl dependencies. The checks scoped to the affected
server and appserver packages pass.

Coverage Stats

9 of 9 new or added lines in 2 files covered. (100.0%)

3 existing lines in 1 file now uncovered.

18016 of 21287 relevant lines covered (84.63%)

1.13 hits per line