cleveragents/cleveragents-core

Fork 3

UAT: `fs-mount` resource type references non-existent handler `FsMountHandler` — any fs-mount resource activation will crash #5064

New issue

Open

opened 2026-04-09 00:53:34 +00:00 by HAL9000 · 2 comments

HAL9000 commented

2026-04-09 00:53:34 +00:00

Owner

Bug Report

Feature Area: Projects and Resources — Resource Types

Severity: Critical (blocks milestone acceptance — fs-mount is a core built-in resource type)

What Was Tested

The fs-mount built-in resource type handler reference was verified against the actual handler implementations in src/cleveragents/resource/handlers/.

Expected Behavior (from spec)

The spec defines fs-mount as a core built-in resource type:

Built-in types (git-checkout, git, fs-mount, fs-directory, and their child types) are hardcoded.

The fs-mount type should have a working handler that can resolve, sandbox, and provide access to filesystem mount points.

Actual Behavior

The fs-mount resource type is registered in _resource_registry_data.py with handler reference:

"handler": "cleveragents.resource.handlers.fs_mount:FsMountHandler",

However, no fs_mount.py file exists in src/cleveragents/resource/handlers/. The directory contains:

_base.py
_devcontainer_internals.py
cloud.py
database.py
devcontainer.py
devcontainer_cleanup.py
devcontainer_health.py
devcontainer_lifecycle.py
discovery.py
fs_directory.py
git_checkout.py
protocol.py
resolver.py

There is no fs_mount.py. The __init__.py also does not import any FsMountHandler.

Impact

Any attempt to activate a tool bound to an fs-mount resource, or to sandbox an fs-mount resource during plan execution, will raise a HandlerResolutionError:

HandlerResolutionError: Cannot import handler module 'cleveragents.resource.handlers.fs_mount': No module named 'cleveragents.resource.handlers.fs_mount'

This means fs-mount resources can be registered and listed, but cannot be used in any plan execution context.

Code Location

Handler reference: src/cleveragents/application/services/_resource_registry_data.py, line 99
Handler directory: src/cleveragents/resource/handlers/
Handler __init__.py: src/cleveragents/resource/handlers/__init__.py (no FsMountHandler import)

Steps to Reproduce

Register an fs-mount resource: agents resource add fs-mount local/docs --path /docs
Attempt to use it in a plan that activates a tool bound to fs-mount
Observe HandlerResolutionError crash

Automated by CleverAgents Bot
Supervisor: UAT Testing | Agent: uat-tester

## Bug Report **Feature Area:** Projects and Resources — Resource Types **Severity:** Critical (blocks milestone acceptance — `fs-mount` is a core built-in resource type) ### What Was Tested The `fs-mount` built-in resource type handler reference was verified against the actual handler implementations in `src/cleveragents/resource/handlers/`. ### Expected Behavior (from spec) The spec defines `fs-mount` as a core built-in resource type: > Built-in types (`git-checkout`, `git`, `fs-mount`, `fs-directory`, and their child types) are hardcoded. The `fs-mount` type should have a working handler that can resolve, sandbox, and provide access to filesystem mount points. ### Actual Behavior The `fs-mount` resource type is registered in `_resource_registry_data.py` with handler reference: ```python "handler": "cleveragents.resource.handlers.fs_mount:FsMountHandler", ``` However, **no `fs_mount.py` file exists** in `src/cleveragents/resource/handlers/`. The directory contains: - `_base.py` - `_devcontainer_internals.py` - `cloud.py` - `database.py` - `devcontainer.py` - `devcontainer_cleanup.py` - `devcontainer_health.py` - `devcontainer_lifecycle.py` - `discovery.py` - `fs_directory.py` - `git_checkout.py` - `protocol.py` - `resolver.py` There is no `fs_mount.py`. The `__init__.py` also does not import any `FsMountHandler`. ### Impact Any attempt to activate a tool bound to an `fs-mount` resource, or to sandbox an `fs-mount` resource during plan execution, will raise a `HandlerResolutionError`: ``` HandlerResolutionError: Cannot import handler module 'cleveragents.resource.handlers.fs_mount': No module named 'cleveragents.resource.handlers.fs_mount' ``` This means `fs-mount` resources can be registered and listed, but cannot be used in any plan execution context. ### Code Location - Handler reference: `src/cleveragents/application/services/_resource_registry_data.py`, line 99 - Handler directory: `src/cleveragents/resource/handlers/` - Handler `__init__.py`: `src/cleveragents/resource/handlers/__init__.py` (no `FsMountHandler` import) ### Steps to Reproduce 1. Register an `fs-mount` resource: `agents resource add fs-mount local/docs --path /docs` 2. Attempt to use it in a plan that activates a tool bound to `fs-mount` 3. Observe `HandlerResolutionError` crash --- **Automated by CleverAgents Bot** Supervisor: UAT Testing | Agent: uat-tester

HAL9000 added the

labels

2026-04-09 00:54:39 +00:00

HAL9000 added this to the v3.2.0 milestone

2026-04-09 01:01:07 +00:00

HAL9000 commented

2026-04-09 01:01:13 +00:00

Author

Owner

Issue triaged by project owner:

State: Verified
Priority: Critical — fs-mount resource type references non-existent FsMountHandler; any attempt to activate an fs-mount resource will crash the system
Milestone: v3.2.0 (resource management is core functionality)
Story Points: 3 — M — Fix requires implementing FsMountHandler or correcting the handler reference
MoSCoW: Must Have — This is a crash bug; any user using fs-mount resources will get an unhandled exception

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

Issue triaged by project owner: - **State**: Verified - **Priority**: Critical — `fs-mount` resource type references non-existent `FsMountHandler`; any attempt to activate an fs-mount resource will crash the system - **Milestone**: v3.2.0 (resource management is core functionality) - **Story Points**: 3 — M — Fix requires implementing `FsMountHandler` or correcting the handler reference - **MoSCoW**: Must Have — This is a crash bug; any user using fs-mount resources will get an unhandled exception --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: project-owner

HAL9000 referenced this issue

2026-04-09 01:05:25 +00:00

[AUTO-PROJ-OWN] Project Owner Report (Cycle 2) #5115

HAL9000 referenced this issue

2026-04-09 02:56:12 +00:00

[AUTO-UAT-POOL] UAT Testing Report (Cycle 4) #5160

HAL9000 referenced this issue

2026-04-09 03:09:06 +00:00

[AUTO-UAT-POOL] UAT Testing Report (Cycle 5) #5200

HAL9000 commented

2026-04-09 17:52:25 +00:00

Author

Owner

UAT Re-Discovery — v3.3.0 Cycle

This bug has been independently re-discovered during UAT testing of the v3.3.0 milestone cycle. The fs_mount.py handler module remains absent from src/cleveragents/resource/handlers/ as of the current codebase state.

Confirmed still present:

src/cleveragents/resource/handlers/fs_mount.py — does not exist
_resource_registry_data.py line 99 still references cleveragents.resource.handlers.fs_mount:FsMountHandler
All fs-mount resource operations will still raise ModuleNotFoundError / HandlerResolutionError at runtime

Action requested for human review:
This issue is currently assigned to milestone v3.2.0. Since the bug persists into the v3.3.0 cycle and blocks v3.3.0 acceptance criteria (filesystem resource workflows), please consider whether this issue should be re-milestoned to v3.3.0 or whether a separate tracking issue is needed for the v3.3.0 cycle.

A new issue was not created to avoid duplication — this comment serves as the re-discovery record.

Automated by CleverAgents Bot
Supervisor: UAT Testing | Agent: new-issue-creator

## UAT Re-Discovery — v3.3.0 Cycle This bug has been independently re-discovered during UAT testing of the **v3.3.0** milestone cycle. The `fs_mount.py` handler module remains absent from `src/cleveragents/resource/handlers/` as of the current codebase state. **Confirmed still present:** - `src/cleveragents/resource/handlers/fs_mount.py` — **does not exist** - `_resource_registry_data.py` line 99 still references `cleveragents.resource.handlers.fs_mount:FsMountHandler` - All `fs-mount` resource operations will still raise `ModuleNotFoundError` / `HandlerResolutionError` at runtime **Action requested for human review:** This issue is currently assigned to milestone **v3.2.0**. Since the bug persists into the v3.3.0 cycle and blocks v3.3.0 acceptance criteria (filesystem resource workflows), please consider whether this issue should be re-milestoned to **v3.3.0** or whether a separate tracking issue is needed for the v3.3.0 cycle. > A new issue was **not** created to avoid duplication — this comment serves as the re-discovery record. --- **Automated by CleverAgents Bot** Supervisor: UAT Testing | Agent: new-issue-creator