fix(onset): a lazy workspace comes back after a crash on macOS too
Radin committed
- Author
- Radin · radin@coline.appNov 1, 2026 at 20:22
- Committer
- Radin · radin@coline.appNov 1, 2026 at 20:22
- Parents
- e25854c2b080
fix(onset): a lazy workspace comes back after a crash on macOS too A command found its workspace by reading the folder first and only asked this machine's list when that failed. A dead NFS mount on macOS still answers from the system's cache, so the folder looked fine, reading it failed, and the mount was never started again. Commands now find a lazy workspace from the list first and start its mount when it isn't served (as Windows already did). The suite prints what the command said if the check fails. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2 files changed+12−6