mirror of
https://github.com/NousResearch/hermes-agent.git
synced 2026-11-16 19:36:54 +00:00
| Filename | Latest commit message | Latest commit date |
|---|---|---|
The #107002 guard keeps an inline ``-c`` program's trailing argv as data. Every Hermes launcher runs the entry point IN the ``-c`` process, so the guard hid real gateways on every OS (#124318, #124588): - the store launcher / Windows updater relaunch (_launchers.runtime_command) - the published launcher script (POSIX shell launcher: every PM-install systemd/launchd gateway) and its Windows .cmd base64 wrapper - the venv_sync re-entry, whose argv is assigned inside the source gateway.status.inline_bootstrap_argv recognises exactly those emitted source shapes, anchored at both ends so a program merely CARRYING one (the restart watcher's respawn argv) still never matches, and rewrites the process to the equivalent ``python -m <entry> <argv>``. /proc, psutil and ``ps`` space-join argv, which splits the source across tokens; the shortest token run ending in a recognised tail is the source whichever reader joined it. Both canonical matchers (looks_like_gateway_command_line and update_cmd_windows._hermes_holder_subcommand) use it. Live on a real PM install (Linux, bwrap): a gateway started through the installed launcher script or runtime_command read "Gateway is not running" on main; with this change both read running, find_gateway_pids and get_running_pid see them. Drops the four #124318 known_failure gates in tests/e2e/core/windows_update. Co-authored-by: Hermes Agent <[email protected]> Co-authored-by: JoaoMarcos44 <[email protected]> Co-authored-by: DianaBudin <[email protected]> |
||
| .. | ||
| __init__.py | ||
| _machine.py | ||
| test_fresh_install_update.py | ||
| test_gateway_across_update.py | ||
| test_git_and_holders.py | ||
| test_interpreter.py | ||
| test_paths_and_acls.py | ||
| test_update_spares_other_installs.py | ||