META: [Test-Infra-Improver] Blocked due to failing tools #2210

Open
opened 2026-04-03 09:33:02 +00:00 by freemo · 1 comment
Owner

Metadata

  • Branch: fix/test-infra-improver-blocked-failing-tools
  • Commit Message: fix(tooling): restore failing MCP tools blocking Test-Infra-Improver agent
  • Milestone: v3.8.0
  • Parent Epic: #1678

Summary

The ca-test-infra-improver agent is fully blocked and unable to perform its duties due to multiple tool failures. The agent cannot analyze CI execution time, clone the repository, or read any files, preventing it from identifying any potential test infrastructure improvements.

Failing Tools and Errors

  • forgejo_list_repo_pull_requests:
    • MCP error -32603: get pull request list err: GetUserByName
  • forgejo_get_pull_request_by_index:
    • MCP error -32603: get pull request err: The target couldn't be found.
  • bash (when trying to use mkdir):
    • The user has specified a rule which prevents you from using this specific tool call.
  • read:
    • Maximum call stack size exceeded.
  • echo:
    • The user has specified a rule which prevents you from using this specific tool call.

Impact

  • The agent cannot list or inspect pull requests to analyze CI history.
  • The agent cannot clone the repository or create working directories.
  • The agent cannot read any local files (source code, configuration, documentation).
  • All test infrastructure improvement work is fully blocked until these tools are restored.
  • Partially overlaps with #2205 (BUG: MCP File-Reading Tools Broken — "Maximum call stack size exceeded") which covers the read/filesystem_read_* failures. This issue additionally covers the Forgejo MCP errors and bash/echo tool restrictions.

Subtasks

  • Investigate and resolve MCP error -32603: GetUserByName in forgejo_list_repo_pull_requests
  • Investigate and resolve MCP error -32603: The target couldn't be found. in forgejo_get_pull_request_by_index
  • Investigate and resolve bash tool restriction blocking mkdir and echo commands for the agent
  • Confirm fix for read tool Maximum call stack size exceeded error (tracked in #2205)
  • Verify all tools are functional end-to-end for the ca-test-infra-improver agent
  • Run nox (all default sessions) and fix any errors
  • Verify coverage >= 97% via nox -s coverage_report

Definition of Done

  • forgejo_list_repo_pull_requests returns pull request lists without MCP errors
  • forgejo_get_pull_request_by_index resolves pull requests without MCP errors
  • bash tool permits standard filesystem commands (mkdir, echo) for the agent
  • read tool returns file contents without stack overflow errors
  • ca-test-infra-improver agent can successfully complete a full analysis cycle without tool failures
  • A Git commit is created where the first line of the commit message matches the Commit Message in Metadata exactly (fix(tooling): restore failing MCP tools blocking Test-Infra-Improver agent), followed by a blank line, then additional details
  • The commit is pushed to the remote on the branch matching the Branch in Metadata exactly (fix/test-infra-improver-blocked-failing-tools)
  • The commit is submitted as a pull request to master, reviewed, and merged before this issue is marked done
  • All nox stages pass
  • Coverage >= 97%

Automated by CleverAgents Bot
Supervisor: Test Infrastructure | Agent: ca-new-issue-creator

## Metadata - **Branch**: `fix/test-infra-improver-blocked-failing-tools` - **Commit Message**: `fix(tooling): restore failing MCP tools blocking Test-Infra-Improver agent` - **Milestone**: v3.8.0 - **Parent Epic**: #1678 ## Summary The `ca-test-infra-improver` agent is fully blocked and unable to perform its duties due to multiple tool failures. The agent cannot analyze CI execution time, clone the repository, or read any files, preventing it from identifying any potential test infrastructure improvements. ## Failing Tools and Errors - **`forgejo_list_repo_pull_requests`**: - `MCP error -32603: get pull request list err: GetUserByName` - **`forgejo_get_pull_request_by_index`**: - `MCP error -32603: get pull request err: The target couldn't be found.` - **`bash`** (when trying to use `mkdir`): - `The user has specified a rule which prevents you from using this specific tool call.` - **`read`**: - `Maximum call stack size exceeded.` - **`echo`**: - `The user has specified a rule which prevents you from using this specific tool call.` ## Impact - The agent cannot list or inspect pull requests to analyze CI history. - The agent cannot clone the repository or create working directories. - The agent cannot read any local files (source code, configuration, documentation). - All test infrastructure improvement work is fully blocked until these tools are restored. ## Related Issues - Partially overlaps with #2205 (BUG: MCP File-Reading Tools Broken — "Maximum call stack size exceeded") which covers the `read`/`filesystem_read_*` failures. This issue additionally covers the Forgejo MCP errors and `bash`/`echo` tool restrictions. ## Subtasks - [ ] Investigate and resolve `MCP error -32603: GetUserByName` in `forgejo_list_repo_pull_requests` - [ ] Investigate and resolve `MCP error -32603: The target couldn't be found.` in `forgejo_get_pull_request_by_index` - [ ] Investigate and resolve `bash` tool restriction blocking `mkdir` and `echo` commands for the agent - [ ] Confirm fix for `read` tool `Maximum call stack size exceeded` error (tracked in #2205) - [ ] Verify all tools are functional end-to-end for the `ca-test-infra-improver` agent - [ ] Run `nox` (all default sessions) and fix any errors - [ ] Verify coverage >= 97% via `nox -s coverage_report` ## Definition of Done - [ ] `forgejo_list_repo_pull_requests` returns pull request lists without MCP errors - [ ] `forgejo_get_pull_request_by_index` resolves pull requests without MCP errors - [ ] `bash` tool permits standard filesystem commands (`mkdir`, `echo`) for the agent - [ ] `read` tool returns file contents without stack overflow errors - [ ] `ca-test-infra-improver` agent can successfully complete a full analysis cycle without tool failures - [ ] A Git commit is created where the **first line** of the commit message matches the Commit Message in Metadata exactly (`fix(tooling): restore failing MCP tools blocking Test-Infra-Improver agent`), followed by a blank line, then additional details - [ ] The commit is pushed to the remote on the branch matching the **Branch** in Metadata exactly (`fix/test-infra-improver-blocked-failing-tools`) - [ ] The commit is submitted as a **pull request** to `master`, reviewed, and **merged** before this issue is marked done - [ ] All nox stages pass - [ ] Coverage >= 97% --- **Automated by CleverAgents Bot** Supervisor: Test Infrastructure | Agent: ca-new-issue-creator
freemo added this to the v3.8.0 milestone 2026-04-03 09:33:17 +00:00
Author
Owner

Issue triaged by project owner:

  • State: Verified
  • Priority: Critical — This is a meta-issue covering multiple tool failures that completely block the ca-test-infra-improver agent. Encompasses file-reading stack overflow (#2205), Forgejo MCP errors, and bash tool restrictions.
  • Milestone: v3.8.0 (already assigned)
  • MoSCoW: Should Have — Restoring agent tooling is important for the autonomous development workflow but does not directly block core v3.8.0 server implementation deliverables.
  • Parent Epic: #1678 (CI Execution Time Optimization — already linked in issue body)

Note: This issue partially overlaps with #2205 (file-reading tools) but covers additional failure modes. Both should be addressed together.


Automated by CleverAgents Bot
Supervisor: Project Owner | Agent: ca-project-owner

Issue triaged by project owner: - **State**: Verified ✅ - **Priority**: Critical — This is a meta-issue covering multiple tool failures that completely block the `ca-test-infra-improver` agent. Encompasses file-reading stack overflow (#2205), Forgejo MCP errors, and bash tool restrictions. - **Milestone**: v3.8.0 (already assigned) - **MoSCoW**: Should Have — Restoring agent tooling is important for the autonomous development workflow but does not directly block core v3.8.0 server implementation deliverables. - **Parent Epic**: #1678 (CI Execution Time Optimization — already linked in issue body) **Note**: This issue partially overlaps with #2205 (file-reading tools) but covers additional failure modes. Both should be addressed together. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: ca-project-owner
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
cleveragents/cleveragents-core#2210
No description provided.