aaa00ae8d2
Roots before the walk: reached as someone else's dependency first, a studio.txt line marked itself seen and skipped its own pin. datasets asks for huggingface-hub>=0.25,<2 and studio.txt pins ==0.36.2, so the pin never got to decide. A start rejected because one is already running is not a spawn failure. The loser was clearing the winner's marker while pip was still inside the venv, which is the one signal an interrupted install leaves behind. A CLI too old for desktop-runtime-check is the CLI those interrupted installs shipped with, and -h passes without touching the backend, so accepting it left exactly those users on the crash path. It is stale for its own reason now; the update installs one that can answer. Owner metadata is removed only while it is still ours. Cleanup after an exit can spend seconds terminating descendants, and a start in that window has already written the next backend's file to the same path. |
||
|---|---|---|
| .. | ||
| 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 | ||