docs(lsp): remove resolved URI limitation
This commit is contained in:
@@ -2,5 +2,5 @@
|
||||
# side as of the last confirmed-consistent state. Both languages carry equal authority;
|
||||
# after editing either side, bring the other along and re-record with:
|
||||
# pnpm run verify-translation-pairing --write packages/lsp/lsp-local/README.md
|
||||
README.md: 2c5ab309f3557ad77696a881b41d164e65bd24fe
|
||||
README.zh.md: d4493832964a5ac0d804602c18774bb106ddcbd9
|
||||
README.md: 299a5282bbca0a6d517af9342c4101cbdae33d4c
|
||||
README.zh.md: edf706fdb424756aa43b303b018b11e3764c2559
|
||||
@@ -55,6 +55,5 @@ No direct invalidation; `dsh-tool-lsp` owns request-prefix changes.
|
||||
## Known Limitations and Deferred Work
|
||||
|
||||
- **No confinement policy** — this package trusts the configured server and does not sandbox its process; a restricted deployment must supply appropriate process/filesystem providers or a same-world sandbox wrapper.
|
||||
- **Execution-world URI rendering** — the stdio host produces provider-owned `file:` URIs. The current model tool renders them with the harness host's path library, so a Windows harness paired with a POSIX remote execution world may show remote locations as URIs or non-native paths; protocol queries remain correct.
|
||||
- **Transient-open compatibility floor** — servers whose synchronization omits open/close (or advertise `None`) are unsupported even if closed-document queries would work; the pinned TypeScript e2e establishes one compatibility floor, not a cross-language claim.
|
||||
- **Per-server/workspace serialization latency** — parallel agents sharing one server and workspace queue behind one process; long-lived workspace processes consume memory until disposal.
|
||||
@@ -55,6 +55,5 @@ Namespace 插件(`name`/`inject`/`Config`/`apply`,无默认导出)
|
||||
## 已知限制与暂缓事项
|
||||
|
||||
- **不提供隔离策略**:这个包(package)信任配置的服务器,不会对其进程执行沙箱化;受限部署必须提供适当的进程/文件系统提供方,或包装同一执行环境的沙箱。
|
||||
- **执行环境 URI 渲染**:stdio 主机生成归提供方所有的 `file:` URI。当前面向模型的工具使用 harness 宿主的路径库渲染这些 URI,因此 Windows harness 与 POSIX 远程执行环境配对时,可能把远程位置显示为 URI 或非本机路径;协议查询仍然正确。
|
||||
- **临时打开兼容性下限**:同步能力省略打开/关闭(或声明 `None`)的服务器不受支持,即使关闭文档查询能够工作;固定的 TypeScript e2e 只建立一项兼容性下限,不代表跨语言承诺。
|
||||
- **逐服务器/Workspace 串行化延迟**:共享同一个服务器与 Workspace 的并行 agent 会在一个进程后排队;长生命周期 Workspace 进程会占用内存直到释放。
|
||||
Reference in New Issue
Block a user