fix(config): resolve uteke data dir at ~/.codecora/uteke (0.10.1 migration) - #208
Merged
Merged
Conversation
…ation) Uteke 0.10.1 migrated the default data directory from ~/.uteke to ~/.codecora/uteke via atomic rename on first launch, so ~/.uteke no longer exists after migration. corin hardcoded ~/.uteke in three config.rs functions, causing: - detect_uteke() false-negative (uteke reported as uninstalled) - detect_uteke_serve_url() ignoring custom [server].host/port - resolve_model_dir() re-downloading the embedding model instead of reusing uteke's migrated copy Fix: check ~/.codecora/uteke (new default, uteke >=0.10.1) first, then ~/.uteke as legacy fallback, in all three functions. Also bump the uteke_client.rs compatibility note from 0.7.x-0.9.x to 0.7.x-0.10.x. Fixes #205
🔍 Cora AI Code Review✅ No issues found. Code looks good! Review powered by cora-cli · BYOK · MIT |
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
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.
Summary
Uteke 0.10.1 migrated the default data directory from
~/.uteke→~/.codecora/uteke(atomicrenameon first launch, old dir gone after migration). corin hardcoded~/.utekein threeconfig.rsfunctions, breaking detection/config/model-reuse on uteke ≥ 0.10.1.Fixes #205.
Root cause — 3 affected functions
detect_uteke()~/.uteke/uteke.dbgone → returnsNone→ uteke reported as uninstalleddetect_uteke_serve_url()~/.uteke/uteke.tomlonly → misses custom[server].host/port, always falls back to defaultresolve_model_dir()~/.uteke/models/...never matches → re-downloads embedding model instead of reusing uteke's migrated copyFix
Check
~/.codecora/uteke(new default, uteke ≥ 0.10.1) first, then~/.utekeas legacy fallback, in all three functions:Also bumped the
uteke_client.rscompatibility note0.7.x–0.9.x→0.7.x–0.10.x.Validation
cargo fmt --all -- --check✅cargo clippy -- -D warnings✅cargo test✅ (18 passed, incl.config::tests::test_detect_uteke_returns_some_if_installed)svelte-check✅ (0 errors)vitest --run✅ (61 passed)npm run build✅Uteke changelog reference
Related