Files
OpenHands/scripts/dev-process-utils.mjs
T
Rohit Malhotraandopenhands edb998220a Remove Docker dependency from dev workflow (#635)
- Delete scripts/dev-docker.mjs and its test
- Simplify package.json: 'npm run dev' now runs local uvx stack directly
  (agent-server + automation + Vite + ingress), no Docker needed
- Remove dev:docker, dev:docker:dynamic, dev:dangerously-dockerless scripts
- Add dev:static for production-build frontend variant
- Update bin/agent-canvas.mjs CLI to use uvx-based stack
- Rename Docker-specific variables: DOCKER_PROJECTS_PATH → PROJECTS_PATH,
  shouldDefaultToDockerProjects → shouldDefaultToProjectsPath
- Update i18n: HOST_HOME_NOT_MOUNTED_HINT no longer references Docker
- Update all docs (README, DEVELOPMENT, SELF_HOSTING, AGENTS.md, CHANGELOG)
- Rename e2e snapshot: docker-workspace-browser → projects-workspace-browser
- Fix all tests to reflect new script names and remove Docker references

Co-authored-by: openhands <openhands@all-hands.dev>
2026-05-19 15:27:25 -04:00

85 lines
2.2 KiB
JavaScript

import process from "node:process";
/**
* Return true while Node still considers the child process active.
*
* Do not use ChildProcess#killed for cleanup decisions. In Node, `killed`
* only means a signal was sent successfully; it does not mean the process has
* exited. That distinction matters for dev launchers because uvx/npm
* wrappers can receive SIGTERM while their long-running child process keeps
* serving on the original port.
*/
export function isProcessRunning(proc) {
return proc.exitCode === null && proc.signalCode === null;
}
/**
* Add spawn options needed for process-tree cleanup.
*
* On POSIX, `detached: true` makes the spawned service the leader of a new
* process group. Later we can signal `-pid` to terminate that whole group,
* including wrapper chains like:
*
* launcher -> uvx -> python agent-server
* launcher -> npm -> sh -> Vite
*
* Windows does not support POSIX process groups, so callers fall back to
* signaling the direct child process there.
*/
export function getProcessTreeSpawnOptions(options = {}) {
return {
...options,
detached: process.platform !== "win32",
};
}
/**
* Signal the whole spawned service tree when possible.
*
* POSIX `process.kill(-pid, signal)` targets the process group whose id is
* `pid`; this only works because services are spawned with
* `getProcessTreeSpawnOptions()`. Without the negative pid, shutdown would
* often stop only the wrapper process and leave the actual server child
* listening on its port.
*/
export function signalProcessTree(proc, signal) {
if (!isProcessRunning(proc)) {
return false;
}
try {
if (process.platform === "win32" || !proc.pid) {
proc.kill(signal);
} else {
process.kill(-proc.pid, signal);
}
return true;
} catch (err) {
if (err?.code === "ESRCH") {
return false;
}
throw err;
}
}
export function createShutdownHookRegistry(onError) {
const hooks = new Set();
return {
add(hook) {
hooks.add(hook);
return () => hooks.delete(hook);
},
run() {
for (const hook of hooks) {
try {
hook();
} catch (err) {
onError?.(err);
}
}
},
};
}