Skip to content

Data Watch 1.5.0: Process stop controls

Latest

Choose a tag to compare

@benaiah-muga benaiah-muga released this 16 Oct 23:50

The Memory tab now lists the individual processes behind each program group, with PID, RAM, and swap. A process owned by your user account can be stopped with SIGTERM from the live details card using a two-step confirmation; processes owned by other users are labelled and cannot be stopped from the dashboard.

Stopping sends the same default signal as the kill command, so the program exits as if asked to close and unsaved work can be lost. Nothing is ever stopped automatically. Process IDs are read live for the dialog and are not saved to history, and the stop endpoint is limited to your own processes, the loopback dashboard, and same-origin requests with the dashboard header.

No runtime dependencies or privileged helper changes are required. Existing memory and network history remains intact.

Validation: 26 Rust tests, clippy with warnings denied, formatting, JavaScript controller checks, a standalone-binary smoke test that stops a real spawned process end-to-end, and a headless Chrome check that clicks through the confirmation and confirms the process exits passed. The pre-existing browser-check timing races (dialog focus restoration, Enter activation, capture-mode wait) were fixed in the test script.

Download the x86-64 Ubuntu archive, verify SHA256SUMS, extract, and run ./data-watch install. The README documents the stop control, its limits, and the SIGTERM behavior.