hermes-agent/tests/test_install_sh_symlink_stomp.py
Tranquil-Flow c75e1a03f9 fix(install): preserve pip entry point when re-running on symlinked install
setup_path() writes the user-facing hermes shim with `cat >`, which
follows existing symlinks. Older installs created
`$command_link_dir/hermes` as a symlink to `$HERMES_BIN`
(`venv/bin/hermes`), so re-running install.sh stomped the pip entry
point with a bash shim that exec'd itself in an infinite loop.

`rm -f` the link target before writing so the shim lands at
`$command_link_dir/hermes` and the venv entry point is left intact.

Adds a regression test that reproduces the symlink-stomp end-to-end
(creates the symlink, drives the real shim-write block from setup_path,
asserts the venv pip script body survives and the shim is now a regular
file). Both new assertions fail on origin/main and pass with the fix.

Closes #21454.
2026-05-14 07:08:45 -07:00

123 lines
4.8 KiB
Python

"""Regression for #21454: re-running install.sh on a symlinked prior install.
Older versions of ``install.sh`` created ``$command_link_dir/hermes`` as a
symlink to the pip-generated entry point at ``$HERMES_BIN`` (i.e.
``venv/bin/hermes``). When ``setup_path()`` later switched to writing a bash
shim with ``cat > "$command_link_dir/hermes" <<EOF``, the redirect followed
the existing symlink and overwrote the pip entry point with the shim. The
shim's ``exec "$HERMES_BIN" "$@"`` then self-recursed and ``hermes`` hung on
every invocation.
These tests pin the fix: ``setup_path()`` must remove ``$command_link_dir/hermes``
before writing through the redirect, so the shim is created as a regular file
in ``command_link_dir`` and the venv entry point is left intact.
"""
from __future__ import annotations
import re
import stat
import subprocess
from pathlib import Path
import pytest
REPO_ROOT = Path(__file__).resolve().parent.parent
INSTALL_SH = REPO_ROOT / "scripts" / "install.sh"
def _extract_setup_path_shim_block() -> str:
"""Return the install.sh shim-write block used by setup_path()."""
text = INSTALL_SH.read_text()
match = re.search(
r"(?P<block>mkdir -p \"\$command_link_dir\".*?chmod \+x \"\$command_link_dir/hermes\")",
text,
re.DOTALL,
)
assert match is not None, (
"Could not locate the setup_path shim-write block in scripts/install.sh"
)
return match["block"]
def test_setup_path_shim_block_removes_old_link_before_writing() -> None:
"""Static guard: the rm must precede the cat heredoc, not follow it."""
block = _extract_setup_path_shim_block()
rm_idx = block.find('rm -f "$command_link_dir/hermes"')
cat_idx = block.find('cat > "$command_link_dir/hermes" <<EOF')
assert rm_idx != -1, (
"setup_path() must `rm -f` $command_link_dir/hermes before the "
"`cat >` heredoc, otherwise an existing symlink (left by older "
"installs) will be followed and the pip entry point overwritten. "
"See #21454."
)
assert cat_idx != -1, "expected `cat >` heredoc still present"
assert rm_idx < cat_idx, (
"`rm -f` must come *before* the `cat >` heredoc, not after."
)
def test_re_running_setup_path_block_preserves_pip_entry_point(tmp_path: Path) -> None:
"""Behavioral repro: simulate prior-install symlink + new-install heredoc.
Layout mirrors a real install:
tmp/
venv/bin/hermes <- pip entry point (the one we must preserve)
local_bin/hermes <- symlink → ../venv/bin/hermes (old install)
Then we run the exact shim-write block from setup_path() with
``HERMES_BIN`` and ``command_link_dir`` pointed at this fixture. The fix
requires that, after the run:
* ``venv/bin/hermes`` still contains its original pip-script body
* ``local_bin/hermes`` is a regular file (not a symlink) holding the shim
"""
venv_bin = tmp_path / "venv" / "bin"
venv_bin.mkdir(parents=True)
pip_entry = venv_bin / "hermes"
pip_marker = "#!/usr/bin/env python\n# pip-generated entry point — must not be overwritten\n"
pip_entry.write_text(pip_marker)
pip_entry.chmod(pip_entry.stat().st_mode | stat.S_IXUSR)
command_link_dir = tmp_path / "local_bin"
command_link_dir.mkdir()
shim_path = command_link_dir / "hermes"
# Reproduce the prior-install state: shim path is a symlink to the
# pip-generated entry point.
shim_path.symlink_to(pip_entry)
assert shim_path.is_symlink()
block = _extract_setup_path_shim_block()
# Drive the block with the real env vars setup_path() sets.
script = f'set -e\nHERMES_BIN={pip_entry!s}\ncommand_link_dir={command_link_dir!s}\n{block}\n'
result = subprocess.run(
["bash", "-c", script],
capture_output=True,
text=True,
cwd=tmp_path,
)
assert result.returncode == 0, (
f"shim-write block failed:\nstdout={result.stdout}\nstderr={result.stderr}"
)
# The pip entry point must still be the original pip script — not a
# re-written self-recursing bash shim.
assert pip_entry.read_text() == pip_marker, (
"venv/bin/hermes was overwritten by setup_path() — symlink-stomp "
"regression (#21454)."
)
# The shim path itself must now be a regular file holding the launcher.
assert shim_path.exists()
assert not shim_path.is_symlink(), (
"command_link_dir/hermes must be replaced with a regular file, not "
"left as a symlink — otherwise the next install will stomp again."
)
shim_text = shim_path.read_text()
assert "unset PYTHONPATH" in shim_text
assert "unset PYTHONHOME" in shim_text
assert f'exec "{pip_entry}"' in shim_text
shim_mode = shim_path.stat().st_mode
assert shim_mode & stat.S_IXUSR, "shim must be user-executable"