Fix: task cancellation bug - Separate agent and task identification #102
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously, the
task_cancelmethod incorrectly usedtask_nameas theagent_namefor RPC routing, causing cancellation requests to be sent to the wrong agent or fail entirely. This fix separates agent identification (who to send the RPC to) from task identification (which task to cancel within that agent).The fix adds
agent_idandagent_nameparameters to properly route cancellation requests to the correct agent, while task identification parameters are passed in the RPC payload. Both agent and task identification are now required and validated.This ensures task cancellation works correctly across the system without breaking existing API compatibility.