Nimblesite / Nimblesite/Basilisk
[LSPUV-CONFIG-BINARY-RESOLUTION] uv binary-resolution cascade is dead code; `executablePath`/`UV_PATH` ignored
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 54
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
Spec: LSPUV-CONFIG-BINARY-RESOLUTION
Spec says:
uv binary resolves via a 5-priority cascade:
basilisk.uv.executablePath→UV_PATH→~/.cargo/bin→~/.local/bin→ PATH.
Code does:
find_uv_binary/is_uv_available implement the cascade exactly but have no caller anywhere. The actual command path (run_uv) spawns a bare uv, so only OS PATH is consulted and priorities 1–4 are silently ignored — basilisk.uv.executablePath has no effect.
Location: crates/basilisk-uv/src/binary.rs vs crates/basilisk-lsp/src/uv_commands.rs (run_uv)
Severity: critical · code logic does not match the spec.
Source: spec↔code conformance audit (PR #203). Full catalogue: docs/plans/SPEC-CONFORMANCE-AUDIT-PLAN.md → CONFAUDIT-CODE-BUG.
Fix per CLAUDE.md TDD bug process: add a failing test that encodes the spec requirement first, then fix the code — never weaken the test.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read crates/basilisk-uv/src/binary.rs and crates/basilisk-lsp/src/uv_commands.rs, then review CLAUDE.md's TDD bug process and the audit entry in docs/plans/SPEC-CONFORMANCE-AUDIT-PLAN.md. Add a failing test for the specified five-priority resolution and verify that run_uv uses the resolved binary rather than a bare uv command.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 64/100