Skip to content

fix(config): resolve uteke data dir at ~/.codecora/uteke (0.10.1 migration) - #208

Merged
ajianaz merged 1 commit into
developfrom
fix/205-uteke-data-dir-codecora-migration
Aug 1, 2026
Merged

fix(config): resolve uteke data dir at ~/.codecora/uteke (0.10.1 migration)#208
ajianaz merged 1 commit into
developfrom
fix/205-uteke-data-dir-codecora-migration

Conversation

@ajianaz

@ajianaz ajianaz commented Aug 1, 2026

Copy link
Copy Markdown
Collaborator

Summary

Uteke 0.10.1 migrated the default data directory from ~/.uteke~/.codecora/uteke (atomic rename on first launch, old dir gone after migration). corin hardcoded ~/.uteke in three config.rs functions, breaking detection/config/model-reuse on uteke ≥ 0.10.1.

Fixes #205.

Root cause — 3 affected functions

Function Symptom on uteke ≥ 0.10.1
detect_uteke() ~/.uteke/uteke.db gone → returns None → uteke reported as uninstalled
detect_uteke_serve_url() reads ~/.uteke/uteke.toml only → misses custom [server].host/port, always falls back to default
resolve_model_dir() priority 1 ~/.uteke/models/... never matches → re-downloads 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:

for base in &[".codecora/uteke", ".uteke"] {
    let default_uteke = home.join(base);
    ...
}

Also bumped the uteke_client.rs compatibility note 0.7.x–0.9.x0.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

0.10.1 — Default data directory migrated from ~/.uteke to ~/.codecora/uteke (#773, #778). First launch auto-migrates via atomic rename.

Related

…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
@github-actions

github-actions Bot commented Aug 1, 2026

Copy link
Copy Markdown

🔍 Cora AI Code Review

No issues found. Code looks good!


Review powered by cora-cli · BYOK · MIT

@ajianaz
ajianaz merged commit a385789 into develop Aug 1, 2026
8 checks passed
@ajianaz
ajianaz deleted the fix/205-uteke-data-dir-codecora-migration branch August 1, 2026 15:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

bug: hardcoded ~/.uteke path breaks with uteke ≥ 0.10.1 (data dir migrated to ~/.codecora/uteke)

1 participant