diff options
| author | Christophe Besson <cbesson@gmail.com> | 2026-10-15 17:42:30 +0200 |
|---|---|---|
| committer | Christophe Besson <cbesson@gmail.com> | 2026-10-15 17:45:41 +0200 |
| commit | 0d082ab4d19412079516b281aff76e8c3f70d9ba (patch) | |
| tree | 46bc48f67663c4049384578c594b8558bce2db6c /packages/meshbay-cli/src/meshbay_cli/complete.py | |
| parent | 41d03f0a35a95daa7d54e7f29ab924776bedf6e4 (diff) | |
| download | meshbay-0d082ab4d19412079516b281aff76e8c3f70d9ba.tar.gz | |
fix(packaging): setup ends a command-line client run from its install
A `meshbay-cli chat --follow` left open holds node-runtime's DLLs, so the
previous version's uninstaller failed ("Failed to uninstall old application
files"), a silent update included, and left the node it had stopped not
running. stop-node.ps1 now ends a meshbay-cli.exe run from this install
(-InstallDir, setup's $INSTDIR), and no other copy.
Found through CIM, not Get-Process: setup runs the 32-bit PowerShell, which
reads no path for a 64-bit process, and the first version of the stop matched
nothing. The test runs the script in that PowerShell. Checked live: an update
over a running follower now ends it, replaces every file and restarts the node.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Diffstat (limited to 'packages/meshbay-cli/src/meshbay_cli/complete.py')
0 files changed, 0 insertions, 0 deletions