gemini-cli - 💡(How to fix) Fix Race Condition in A2A Task Execution Tracking [1 comments, 2 participants]

What happened?

The check for whether a task is already executing (executingTasks.has(taskId)) and the subsequent executingTasks.add(taskId) are not atomic.

What did you expect to happen?

Task execution state should be managed using atomic operations or a locking mechanism to prevent multiple primary loops for the same task.

Client Information

<details> <summary>Client Information</summary>

OS: linux Date: Sunday, May 10, 2026 Gemini CLI: 0.42.0-nightly

</details>

Login information

Automated audit with Gemini CLI.

Anything else we need to know?

File: packages/a2a-server/src/agent/executor.ts, Lines 355-385. If two requests for the same task arrive nearly simultaneously, they could both start as 'primary' executions, leading to corrupted state.

Severity: Medium Area: area/core