You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix: launch leased-continuation CLI through the selected test Python
Review follow-up. The new CLI test started `promisify(execFile)("python3", …)`,
so the bare system interpreter (Python 3.9 on this host) ran `loopx.cli` and
failed on `@dataclass(slots=True)`; only a PATH-injected `uv run` hid it. The
merged checkout guard in `test_python_runtime.test.ts` also missed the curried
call shape, so it let the regression through.
Both subprocesses now take their interpreter from
`scripts/test-python.mjs`, and the guard sees through promisified and aliased
launchers while still ignoring a resolved interpreter path or an unrelated
helper argument.
Verified with the system Python 3.9 in PATH and no `uv` wrapper: the bare
`node --experimental-strip-types --test` run of the new suite reports 10
passed, 1 skipped (PostgreSQL), and restoring the literal `python3` launch
makes the guard name the file.
Signed-off-by: huangruiteng <14976749+huangruiteng@users.noreply.github.com>
"import json,sys; from pathlib import Path; from loopx.control_plane.todos.active_state_todo_parser import parse_todo_source; rows=parse_todo_source(Path(sys.argv[1]).read_text())[0]['agent']; print(json.dumps(next(r for r in rows if r['todo_id']==sys.argv[2])))",
0 commit comments