mirror of
https://github.com/open-jarvis/OpenJarvis.git
synced 2026-07-28 14:07:55 +00:00
krypticmouseandClaude Opus 4.7
612d3e1f88
Addresses the second half of the Discord support thread on the "Jarvis server did not become healthy in time" issue (PR #398 fixed the diagnostic gap; this fixes discoverability of the right install path so users don't end up there in the first place). Three changes, all surface improvements: 1. **`README.md`** — explicit Windows section in the Installation block. Previously, the only Windows mention was a footnote ("Platforms: ... WSL2 on Windows") that came AFTER the `curl … | bash` install command. Users on PowerShell would copy/paste the command, get a syntax error, then try to debug bash on Windows. Now the README clearly says: bash installer is macOS/Linux only; Windows users have two paths (WSL2 with one-time `wsl --install` setup, or the desktop .exe from Releases). Both link to the relevant docs. 2. **`scripts/install/install.sh`** — early bail when running under Git Bash / MSYS2 / Cygwin (MINGW*, MSYS*, CYGWIN* per `uname -s`). These environments aren't WSL — `uv` and `git` will install to Windows-side paths that OpenJarvis can't reach, Ollama integration silently breaks, and the user gets to debug it 3 minutes into a doomed install. The bail message points at both the WSL2 setup command (`wsl --install -d Ubuntu-24.04`) and the desktop .exe download as alternatives. Verified the case-match doesn't fire on Linux (`uname -s` → `Linux`, matches the wildcard fall-through, not the MINGW patterns). 3. **`frontend/src-tauri/src/lib.rs`** — when `resolve_bin("uv")` can't find uv, the per-OS error message now contains the exact install command for the user's OS, ready to copy/paste. On Windows that's the `irm https://astral.sh/uv/install.ps1 | iex` command Marc kept reposting on the Discord support thread (5/12-5/14). On macOS/Linux it's the standard `curl | sh` installer. The previous generic "Install it from https://astral.sh/uv" left users guessing whether to use winget, scoop, pip, or the official installer — which is exactly the confusion the Discord thread captured. None of these are root-cause code fixes (Discord users' uv installs fail for environment-specific reasons we can't diagnose remotely), but together they remove the three biggest friction sources we saw: copy-paste install command that can't possibly work, doomed git-bash installs that fail mysteriously, and missing exact install commands when uv isn't found. The Tauri change ships in the desktop binary; the README change is visible immediately on the repo page; the install.sh change reaches users via openjarvis.ai (when it's restored) and via the GitHub-raw fallback from PR #398. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>