socialmag-dash crash-looped on a real box. WorkingDirectory was the repo and
ExecStart was `python -m http.server`, so socketserver's `import selectors`
found the repo's selectors.py and the unit died with "module 'selectors' has no
attribute 'SelectSelector'" every 5 seconds. :8321 never bound.
This is the SAME root cause already fixed twice this evening — once for
`-m socialmag` (console scripts, cli.py) and once for `-m venv` (run python
from /). Both fixes were about keeping the repo off sys.path, and then the unit
file put it right back on. A `-m` anywhere near this directory is the hazard,
not any particular entry point.
The dash now serves with --directory and sits in / instead of standing in the
tree it serves. The by-hand fallback instructions carried the identical bug and
now do the same, with a line saying why.
openbridge and refresh were never affected: they exec console scripts, which do
not put the working directory on sys.path. That is exactly why cli.py exists.
The real fix is renaming selectors.py and queue.py. Until then this trap keeps
finding new ways in, and that is not a prediction — it is three for three.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
A clone + ./install.sh + ./launch-brave.sh + sign in once. Nothing else.
pyproject.toml declares the one real dependency (websockets) and maps the
repo-root-is-the-package layout, which retires the PYTHONPATH=<parent> line
every unit used to carry.
cli.py backs three console scripts. They exist because `python3 -m socialmag`
run from INSIDE a clone dies at `import asyncio`: the repo root is the package
dir, so it ships selectors.py and queue.py, and python puts the current
directory first on sys.path. `cd socialmag` is the first thing anyone does
after a clone, so the documented workaround failed at exactly the moment it
would be tried. A generated bin/ script never puts cwd on sys.path.
The same trap bit `python3 -m venv` inside install.sh — the installer was
broken by the thing it exists to fix. Every python3 call now runs from /.
deploy/user/*.in replaces root system units with systemd --user templates:
no User=, WantedBy=default.target, venv paths, @REPO@/@VENV@/@CDP_ENDPOINT@
substituted at install time. deploy/home/ is untouched and still live here.
launch-brave.sh carries --disable-background-timer-throttling. That is
load-bearing, not tidiness: five of six platforms are read in a hidden tab, and
a throttled background tab stops running the timers those pages use to fetch
their own data — the reads come back empty with no error.
install.sh checks the mcp package in hermes's own interpreter and refuses to
continue without it. Hermes treats mcp as optional and silently no-ops the
whole subsystem when it is missing, so a server that never loaded looks exactly
like one that loaded and did nothing.
It will not merge into an existing mcp_servers: key — it backs up config.yaml
and appends only when the key is absent, otherwise it prints the block. Blind
YAML merging is how someone's other servers disappear.
Verified end-to-end in a sandbox with a fake HOME and stubbed systemctl:
real MCP initialize handshake from inside the repo dir returns all 7 tools;
hermes's own yaml parser re-reads the written config with every pre-existing
key intact; a second run leaves the mcp_servers key count at 1; launch-brave.sh
exits 1 against a busy port; no unsubstituted @PLACEHOLDER@ in any rendered unit.
Not fixed, pre-existing: server.py reports SERVER_VERSION 0.1.0 while the repo
is at v0.7. The handshake shows 0.1.0.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
juxtapoandClaude Opus 5