## Summary
Reported as "deliver_files is broken". It is not: **the tool never ran.**
Every `deliver_files` call on one install was refused before dispatch -- five in a row in a single session -- and nothing was ever delivered:
```
Error: Invalid parameters for tool 'deliver_files': files should be array
```
What the model sent was the array, spelled as a string:
```json
{"files": "[{\"path\": \"...poster.png\", \"title\": \"...\"}]", "message": "..."}
```
`cast_params` already forgives that spelling for every scalar type -- `"3"` for an integer, `"true"` for a boolean -- and did not for arrays or objects, which are exactly the types a model is most likely to stringify.
## Type
- [x] Fix
- [ ] Feature
## The edge of the forgiving is the design
When the value is a string, try `json.loads`, and take the result **only if it is the type the schema asked for**. A string that is not JSON, or is JSON of the wrong shape, is returned unchanged so the validator still names the real problem -- the point is to widen what is accepted, not to swallow a type error.
**Nothing here can raise.** Turning "your argument has the wrong type" into a traceback would be worse than the refusal it replaces, so the parse is wrapped and failure falls through.
**A `type: "string"` field is never parsed.** JSON is ordinary text in a message body or a file's content, and replacing it would hand the tool something it never asked for. Two independent things prevent it today (the string branch returns before the parse is reached, and the parse only wins on a type match), which is why the case pinning it is a tripwire rather than a load-bearing assertion -- said so in its own docstring rather than left to look like coverage.
## Not just deliver_files
Six built-in tools declare an array or object parameter and were all exposed:
| tool | parameter |
|---|---|
| `deliver_files` | `files` |
| `ask_user` | `questions` |
| `image_generate` | `images` |
| `message` | `media` |
| `create_playbook` | `skills` |
| `video_generate` | `params` |
The same failure was already seen from the other side: `acp_client/acp_agent.py` records `update_task_state` and `operations should be array` from a real dispatch.
## Verification
```
make lint-python ruff check + ruff format --check, 1850 files
make lint-imports 9 contracts kept, 0 broken
pytest tests/ 19,699 passed, 7 failed (all pre-existing, see below)
```
- [x] Relevant tests pass locally
- [x] Relevant lint / type checks pass locally
- [ ] User-facing docs or screenshots -- no user-facing string
**End to end, through the real tool**, with the exact payload that failed five times in production:
```
files sent as: str -> [{"path": ".../poster.png", "title": "..."}]
returned: Delivered 1 file(s): poster.png (72 B).
still "should be array": False
registered in the store: True
```
Twelve cases, five mutations, each killing at least one:
| mutation | red |
|---|---|
| drop the whole branch (the old behaviour) | 3 |
| raise instead of falling through on a parse failure | 5 |
| accept the parse whatever type it yielded | 1 |
| do not re-cast the parsed value, so items are not cast | 1 |
| widen the tuple to include `string` | **survived -- unreachable** |
The last is worth stating rather than hiding: that mutation cannot change behaviour, because the `type == "string"` branch returns earlier and the type check would refuse the result anyway. I also tried moving the new block above that branch, alone and combined with widening the tuple, and neither reddens anything either. The invariant holds by construction; the case that documents it says so.
**Pre-existing failures, checked against the base.** 7 failed in the full run, all in `tests/test_security_network.py` (`test_a_redirect_to_a_dangerous_address_is_refused` and siblings). Running that file alone on this same tree gives 4 -- the count is order-dependent -- and the change touches only `raven/agent/tools/params.py` plus a new test file, neither of which `raven/security/network.py` imports. The failures are the box's resolver: it returns poisoned answers roughly half the time, which I measured separately (`en.wikipedia.org` came back as `2001::1` on 3 of 6 lookups). Not introduced here, and worth someone's attention on its own.
## Risk
- [x] Security impact considered -- widens what reaches a tool's own validation, not what bypasses it. A parsed value is still validated against the same schema, and a parse that yields the wrong type is refused exactly as before
- [x] Backward compatibility considered -- a call that worked before takes the identical path; the new branch is reached only by a `str` where an array or object is declared, which previously always failed
- [x] Rollback path is clear -- single-commit revert
## Related Issues
N/A
## Swept
`mr-review-patterns` pre-submit sweep, over `git diff origin/main...HEAD`.
- **1 (a write location moved)** -- nothing moved; a branch was added to an existing dispatch on `target_type`. Grepped every caller of `cast_params`: the registry is the only one, and it runs `validate_params` right after, which is the reader this affects.
- **2 (a value with several entry points)** -- the cast is the single funnel every tool argument passes through, which is why the fix belongs here and not in `deliver_files`.
- **3 (a guard)** -- checked both directions: what it wrongly lets through (JSON of the wrong type, non-JSON text -- both refused, with cases) and what it wrongly refuses (a real list, unaffected, with a case).
- **4 (tests)** -- five mutations above, one honestly reported as unreachable. Failing-ID sets diffed against the base rather than counts.
- **6 (stale text)** -- the module docstring enumerated what is coerced ("a string that should be an integer"); it now names arrays and objects too. Grepped the tracked tree for other statements of the rule: none.
- **9 (error handling)** -- the new path adds one way to end and it is caught: `json.loads` raises `ValueError` on bad text and `TypeError` on a non-string, and both fall through to the untouched value.
- **11** -- `git ls-files | grep -c node_modules` is 0; the commit-message gate was run, not eyeballed.
Not applicable, with reasons: **3b, 3c, 3d, 3e** (no tool schema produced, no state moved, one lane, no assertion lost its symbol); **4b, 4c, 4d** (no platform branch, no shell, no rendered number); **5, 5b** (no dependency; `json` is stdlib and already imported across this package); **6b, 6c** (no backup, no generated artifact); **7, 7b** (nothing on disk); **8** (no asset, no secret); **10** (no prompt text).
## Deliberately not fixed
The error text still ends with `[Analyze the error above and try a different approach.]`, and the model plainly did not -- it sent the same shape five times. A message naming the expected spelling (`files must be a JSON array, not a string containing one`) would give it something to act on. That is a change to the registry's error surface, affects every tool, and deserves its own argument.
## Moved from !594
Opened on a compliant source branch. AGENTS.md 2.1 asks for a 3-5 word snake_case description and the previous branch had seven; GitLab cannot change an existing merge request's source branch, so the change moves rather than the name.
Same commits, rebased onto `c2a9768f`. Both code findings from the review on !594 are already in them -- `RecursionError` caught with its regression case, and the implementation comment reduced to the two non-obvious reasons. Nothing else changed, so that review carries.
185 lines
6.4 KiB
Python
185 lines
6.4 KiB
Python
"""Contributed background services: a resident host runs them, and owns them.
|
|
|
|
The lifecycle half of the services seam: the loop starts what the assembly
|
|
attached, exactly once, minting each service the same namespaced grants a
|
|
tool receives at bind time; a service that fails to start is left out
|
|
loudly; stop runs newest-first and is idempotent. Disposal order is pinned
|
|
by the dispose-roster guard beside the swap tests. The contributed session
|
|
observers ride this same lifecycle: attached to the session store when the
|
|
services start, detached when they stop, never attached on a one-shot host.
|
|
"""
|
|
|
|
from __future__ import annotations
|
|
|
|
import pytest
|
|
|
|
from raven.agent.loop import AgentLoop
|
|
from raven.agent.loop.bundles import HostWiring, ToolWiring, TurnPolicy
|
|
from raven.contracts.llm_provider import LLMResponse
|
|
from raven.providers.base import LLMProvider
|
|
|
|
|
|
class _Provider(LLMProvider):
|
|
def __init__(self) -> None:
|
|
super().__init__(api_key="test")
|
|
|
|
async def chat(
|
|
self,
|
|
messages,
|
|
tools=None,
|
|
model=None,
|
|
max_tokens=4096,
|
|
temperature=0.7,
|
|
reasoning_effort=None,
|
|
tool_choice=None,
|
|
):
|
|
return LLMResponse(content="ok", finish_reason="stop")
|
|
|
|
def get_default_model(self) -> str:
|
|
return "fake/default"
|
|
|
|
|
|
class _Service:
|
|
def __init__(self, name: str, log: list) -> None:
|
|
self.contributed_by = name
|
|
self._log = log
|
|
self.handles = None
|
|
|
|
async def start(self, handles) -> None:
|
|
self.handles = handles
|
|
self._log.append(f"start:{self.contributed_by}")
|
|
|
|
async def stop(self) -> None:
|
|
self._log.append(f"stop:{self.contributed_by}")
|
|
|
|
|
|
class _Explosive(_Service):
|
|
async def start(self, handles) -> None:
|
|
raise RuntimeError("no thanks")
|
|
|
|
|
|
def _loop(tmp_path, cron=None) -> AgentLoop:
|
|
loop = AgentLoop(
|
|
provider=_Provider(),
|
|
workspace=tmp_path,
|
|
model="fake/model",
|
|
policy=TurnPolicy(max_iterations=2),
|
|
host=HostWiring(cron_service=cron),
|
|
tools=ToolWiring(restrict_to_workspace=True),
|
|
)
|
|
return loop
|
|
|
|
|
|
@pytest.mark.asyncio
|
|
async def test_start_is_once_stop_is_reversed_and_both_are_idempotent(tmp_path):
|
|
log: list[str] = []
|
|
a, b = _Service("plug-a", log), _Service("plug-b", log)
|
|
loop = _loop(tmp_path)
|
|
loop.plugin_services = (a, b)
|
|
|
|
await loop.start_plugin_services()
|
|
await loop.start_plugin_services()
|
|
assert log == ["start:plug-a", "start:plug-b"], "started once each, in order"
|
|
assert a.handles is not None and a.handles.wake_scheduler is None, "no scheduler on this host"
|
|
|
|
await loop.stop_plugin_services()
|
|
await loop.stop_plugin_services()
|
|
assert log == ["start:plug-a", "start:plug-b", "stop:plug-b", "stop:plug-a"], "newest first, once"
|
|
|
|
|
|
@pytest.mark.asyncio
|
|
async def test_a_failing_service_is_left_out_loudly_and_the_rest_run(tmp_path):
|
|
log: list[str] = []
|
|
bad, good = _Explosive("plug-bad", log), _Service("plug-good", log)
|
|
loop = _loop(tmp_path)
|
|
loop.plugin_services = (bad, good)
|
|
|
|
await loop.start_plugin_services()
|
|
assert log == ["start:plug-good"]
|
|
|
|
await loop.stop_plugin_services()
|
|
assert log == ["start:plug-good", "stop:plug-good"], "the failed starter is never stopped"
|
|
|
|
|
|
@pytest.mark.asyncio
|
|
async def test_a_started_service_receives_the_namespaced_wake_grant(tmp_path):
|
|
from raven.proactive_engine.schedulers.cron.service import CronService
|
|
|
|
log: list[str] = []
|
|
svc = _Service("plug-a", log)
|
|
cron = CronService(tmp_path / "jobs.json", allowed_channels=None)
|
|
loop = _loop(tmp_path, cron=cron)
|
|
loop.plugin_services = (svc,)
|
|
|
|
await loop.start_plugin_services()
|
|
granted = svc.handles.wake_scheduler
|
|
assert granted is not None
|
|
import time
|
|
|
|
job = granted.schedule_wake("c1", int(time.time() * 1000) + 60_000, "look", channel="tui")
|
|
assert job.id == "wake:plug-a:c1", "the same namespaced grant a tool gets at bind"
|
|
|
|
|
|
class _Heard:
|
|
def __init__(self) -> None:
|
|
self.calls: list[tuple[str, bool]] = []
|
|
|
|
def on_session_deleted(self, session_key: str, removed: bool) -> None:
|
|
self.calls.append((session_key, removed))
|
|
|
|
|
|
@pytest.mark.asyncio
|
|
async def test_start_attaches_the_observers_and_stop_detaches_them(tmp_path):
|
|
"""[code seam-2] Attach rides the services lifecycle -- even with zero
|
|
services contributed -- and both verbs stay idempotent."""
|
|
observer = _Heard()
|
|
loop = _loop(tmp_path)
|
|
loop.session_observers = (observer,)
|
|
assert loop.sessions._delete_observers == (), "assembly attaches nothing"
|
|
|
|
await loop.start_plugin_services()
|
|
await loop.start_plugin_services()
|
|
assert loop.sessions._delete_observers == (observer,), "attached once, replacement semantics"
|
|
|
|
loop.sessions.delete("tui:lifecycle01")
|
|
assert observer.calls == [("tui:lifecycle01", False)]
|
|
|
|
await loop.stop_plugin_services()
|
|
await loop.stop_plugin_services()
|
|
assert loop.sessions._delete_observers == ()
|
|
loop.sessions.delete("tui:lifecycle02")
|
|
assert len(observer.calls) == 1, "a detached observer hears nothing"
|
|
|
|
|
|
@pytest.mark.asyncio
|
|
async def test_a_one_shot_host_never_attaches_observers(tmp_path):
|
|
"""A one-shot turn never starts the plugin services, so its deletes fire
|
|
no observer -- the seam is zero-cost for every non-resident host."""
|
|
observer = _Heard()
|
|
loop = _loop(tmp_path)
|
|
loop.session_observers = (observer,)
|
|
|
|
loop.sessions.delete("tui:oneshot01")
|
|
assert observer.calls == []
|
|
assert loop.sessions._delete_observers == ()
|
|
|
|
|
|
def test_every_resident_host_starts_and_stops_the_services() -> None:
|
|
"""[seam-2] The resident hosts are exactly three assemblies: the gateway's
|
|
generation loop, the rpc stack (serving the page and acp connections), and
|
|
the tui's hand-built server. Each must both start and stop the services --
|
|
a host that starts what it never stops leaks producers into teardown, and
|
|
one that stops what it never started is a dead affordance."""
|
|
import inspect
|
|
|
|
from raven.cli import gateway_commands, tui_commands
|
|
from raven.rpc import bootstrap
|
|
|
|
for name, src in (
|
|
("build_rpc_stack", inspect.getsource(bootstrap.build_rpc_stack)),
|
|
("tui server", inspect.getsource(tui_commands._run_rpc_server_until_done)),
|
|
("gateway", inspect.getsource(gateway_commands.register)),
|
|
):
|
|
assert "start_plugin_services" in src, f"{name} never starts the services"
|
|
assert "stop_plugin_services" in src, f"{name} never stops the services"
|