zara-memory: normalize native symbolic-memory OS launch failures #122

New issue

Closed

opened 2026-09-08 02:03:01 +00:00 by nsaspy · 0 comments

nsaspy commented

2026-09-08 02:03:01 +00:00

Owner

Problem

SymbolicMemoryMCP._call() translates missing executables, non-zero exits, and timeouts into SymbolicMemoryMCPError, but other process-launch OSError subclasses (for example PermissionError from a configured non-executable file) escape raw. The plugin start path checks that an absolute executable is a file, not that invocation will succeed, so this is a reachable configuration failure boundary.

Required behavior

process launch OSError failures are translated to SymbolicMemoryMCPError;
no command retry or shell fallback is introduced;
fixed argv, timeout, sanitized environment, and backend error handling remain unchanged;
deterministic tests prove the runner failure is normalized;
full compatibility/registry/plugin/Nix package gates stay green.

Advances honest optional-backend degradation under #7.

## Problem `SymbolicMemoryMCP._call()` translates missing executables, non-zero exits, and timeouts into `SymbolicMemoryMCPError`, but other process-launch `OSError` subclasses (for example `PermissionError` from a configured non-executable file) escape raw. The plugin start path checks that an absolute executable is a file, not that invocation will succeed, so this is a reachable configuration failure boundary. ## Required behavior - process launch `OSError` failures are translated to `SymbolicMemoryMCPError`; - no command retry or shell fallback is introduced; - fixed argv, timeout, sanitized environment, and backend error handling remain unchanged; - deterministic tests prove the runner failure is normalized; - full compatibility/registry/plugin/Nix package gates stay green. Advances honest optional-backend degradation under #7.

nsaspy closed this issue

2026-09-08 02:03:01 +00:00