mirror of
https://github.com/getpaseo/paseo.git
synced 2026-11-05 16:04:43 +00:00
Mohamed Boudra
8dfdb479ab
On 0.15.0 the daemon launches the detached terminal worker while it is being created, and the worker refuses to start unless it can read its own birth time and command line (Windows PowerShell 5.1 `Get-CimInstance`, `ps` elsewhere). Any failure of that query used to escape startWorkerTerminalManager and take the whole daemon down with "Daemon failed to start (exit 1)", as two Windows machines hit after the update: one whose PowerShell 5.1 cannot load CimCmdlets, one where powershell.exe cannot be spawned at all. 0.14.0 never ran that query at startup. The launch error is now logged and the daemon starts without a current worker. The pool already launches one lazily on the first terminal creation, so that request reports the same error while the machine still cannot run the query, and terminals come back once it can. The identity requirement itself is unchanged: a worker without a verified identity is never written or adopted.