mirror of
https://github.com/hanzoai/lsp.git
synced 2026-09-30 22:52:48 +00:00
zooqueenandHanzo Dev
88a8f28fa9
Rust answered four queries in five against a warm root. The fifth came back `rpc -32801: content modified`, which the daemon passed up as an error and the door turned into a 502. -32801 is the protocol's one retryable answer: the server computed against state it has since replaced, so the result is stale rather than wrong, and the spec has the client ask again. rust-analyzer says it for anything asked while a workspace is still loading, which is exactly when a cold root is queried. Retried in Call, so every op gets it without each caller learning the code, and bounded twice over: a few attempts, and the caller's context underneath that. A server that never settles still ends as an error rather than a request that never returns. Co-authored-by: Hanzo Dev <[email protected]>
lsp
The jailed language-server daemon. It holds immutable per-(org, repo, commit) working trees, runs a language server over each one inside a jail with no network, and answers position questions about them.
The answer it exists for is a definition that leaves the repository and lands in a dependency — which a static symbol index structurally cannot give you.
POST /root {org, repo, rev, files} → {ready, cold, langs}
POST /root/warm same body, only for a held repo
POST /ask {org, repo, rev, op, path, line, character, relation}
→ the answer, or 409 {"need":"tree"}
GET /healthz liveness
GET /readyz readiness — green only once the jail proved out on this host
Everything else — the wire contract in full, the two-phase security model, the deployment, and what phase 2 is — is in LLM.md.