f749c90d87
install.sh decides on elevation at :1931, before it creates the venv at :2120, so only a spawn failure and that exit prove pip never ran. A nonzero exit or a failed wait can land part-way through replacing a package, and the runtime probe does not reach transitive dependencies, so clearing the marker there throws away the only remaining signal. Also treat a hung CLI as stale on its own timeout rather than falling through to two more probes, and let repair report an environment the backend rejects instead of reinstalling over a healthy tree. |
||
|---|---|---|
| .. | ||
| capabilities | ||
| icons | ||
| linux | ||
| src | ||
| windows | ||
| build.rs | ||
| Cargo.lock | ||
| Cargo.toml | ||
| Entitlements.plist | ||
| Info.plist | ||
| tauri.conf.json | ||
| tauri.macos.conf.json | ||
| tauri.windows.conf.json | ||