fix(windows): HTTP-first version gate + PATHEXT CLI discovery#180
Merged
Conversation
On Windows the Documents tab always showed "uteke CLI not found" /
"Detected: unknown" even with uteke.exe correctly on PATH, because the
Documents version gate fell back to shelling the CLI and the CLI lookup
missed the .exe extension. Two-pronged fix:
1. HTTP-first version resolution (the real fix). resolve_uteke_version
now probes the running server's /health `version` field for LOCAL
servers too, not just remote ones. The connected uteke-serve already
reports its version over HTTP (>= 0.7.2, #636), so the gate no longer
depends on locating the CLI binary at all for any modern install.
The cached `uteke --version` CLI output remains as a fallback for
servers older than 0.7.2 that don't report /health version.
2. PATHEXT-aware CLI discovery (fixes the fallback + self-update path).
- find_in_path now probes every PATHEXT extension on Windows
(uteke.exe, uteke.com, ...) per PATH entry.
- find_uteke_cli / find_uteke_serve try the .exe variants in
~/.local/bin as well.
- PATHEXT parsing extracted into a pure `expand_with_pathext` helper
(cfg-gated) with 3 cross-platform unit tests, since CI runs only
on Linux.
Verified locally: cargo fmt/clippy(-D warnings)/test (17), svelte-check
(0 err), vitest (61), npm build.
🔍 Cora AI Code Review🟡 Warning (1)
Review powered by cora-cli · BYOK · MIT |
Merged
ajianaz
added a commit
that referenced
this pull request
Jul 20, 2026
Patch release — Windows Documents-tab fix, uteke 0.8.x compatibility, and a full dependency sweep (incl. vite 6→8). - bump version 0.3.1 → 0.3.2 (package.json, Cargo.toml, Cargo.lock, tauri.conf.json) - CHANGELOG entry Contents (since v0.3.1): - Fixed: Windows "uteke CLI not found" — HTTP-first version gate reads /health `version`; CLI discovery now PATHEXT-aware (#171, #180) - Fixed: uteke 0.8.x room-document compat — /room/summary-document with legacy /room/document fallback (#178) - Changed: version gate HTTP-first for local servers too (#180) - Deps: vite 6→8 + @sveltejs/vite-plugin-svelte 5→7 (#179), tokio 1.52→1.53 (#175), serde/thiserror/toml/tauri-plugin-dialog, @codemirror/language/dompurify/marked, actions/setup-node 6→7 (#172)
This was referenced Jul 20, 2026
Merged
ajianaz
added a commit
that referenced
this pull request
Jul 21, 2026
Version detection no longer shells `uteke --version` on the data/version path. The effective uteke version is resolved purely from the connected server's /health `version` field (uteke ≥ 0.7.2) in resolve_uteke_version — same path for local and remote servers. Changes: - Remove the AppState.uteke_version cache field + its startup CLI probe. - resolve_uteke_version: merge the local/remote branches into one HTTP-only path (no cached fallback). Returns None when the server is unreachable or older than the /health version field. - uteke_self_update: drop the now-dead cache write (keeps `uteke upgrade` + detect_uteke_version to read the freshly-upgraded CLI version — the one remaining CLI touch, which is binary maintenance, not data). Net effect: CorIn ↔ uteke-serve is HTTP-only for all data + version gating. The `uteke` CLI binary is invoked only by the explicit "Update uteke" action (and by bootstrap, which spawns the uteke-serve daemon). This completes the HTTP-first direction started in #180 and fully removes the CLI-discovery fragility that caused #171 on Windows. Docs: compat comments updated to uteke 0.7.x–0.9.x; module doc notes /room/summary-document is canonical since uteke 0.9.0. Verified: cargo fmt/clippy(-D warnings)/test (17), svelte-check (0 err), vitest (61), npm build.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #171.
Root cause: the Documents version gate probed
uteke --versionvia the CLI, and the CLI lookup (find_in_path/find_uteke_cli) did not handle the Windows.exeextension /PATHEXT. Result: on Windows, "uteke CLI not found" → "Detected: unknown" → Documents tab blocked, even though uteke.exe was correctly installed and the HTTP connection to uteke-serve worked (Memories & Graph fine).Two-pronged fix:
HTTP-first version gate (the real fix).
resolve_uteke_versionnow probes the running server's/healthversionfield for local servers too (previously only remote). The connected uteke-serve reports its version over HTTP (≥ 0.7.2, #636), so the gate no longer depends on locating the CLI binary for any modern install — including the reporter's uteke 0.8.0 on Windows. Cacheduteke --versionstays as fallback for servers < 0.7.2.PATHEXT-aware CLI discovery (fixes the fallback + self-update).
find_in_pathprobes everyPATHEXText per PATH entry on Windows;find_uteke_cli/find_uteke_servetry.exein~/.local/bin. PATHEXT parsing extracted into a pureexpand_with_pathexthelper (#[cfg(any(windows, test))]) with 3 cross-platform unit tests.Testing note: runtime behavior verified via logic/unit tests on macOS. CI runs Linux-only (
ci.yml), so the Windows branches are covered by (a) the pure unit tests and (b) the release build matrix (windows-latest). The reporter on Windows can confirm a build.All checks green locally: cargo fmt/clippy(-D warnings)/test (17), svelte-check (0 err), vitest (61), npm build.