Skip to content

RimeJev 0.3.0 · Tev & model timeouts

Choose a tag to compare

@IIIIOvOIIII IIIIOvOIIII released this 11 Oct 09:40
· 19 commits to main since this release

鼠须管 Jev 0.3.0 / RimeJev 0.3.0

中文

新增本地 Tev1 0.8B、4B,与 this-that-model 1.2 和 Jev 云端按应用自由切换。候选来源统一为 ✦ Jev、✦ TT、✦ Tev。

每个模型有独立的超时设置(0.3–10 秒),支持保存和恢复默认。Jev、TT、Tev 0.8B 默认 0.6 秒,Tev 4B 默认 2 秒;计时包含输入防抖及候选采样。原生候选立即可用,超时或模型失败不会阻碍选词。

保留原首选;推荐命中首选时仅加标记,否则移到第二位,其余候选保持相对顺序。模型切换会作废旧请求,等待旧模型释放再加载新模型。下载完成后自动重新加载当前所选模型。

Tev 使用固定版本的独立本机运行组件,不替换系统 Ollama。所有权重、运行组件、凭据、个人词库及本机配置均不随仓库发布。

这是 Apple Silicon / macOS 14+ 的源码版本。安装助手请遵循 LLM_INSTALL.md。模型对中文语境可能给出低置信度或错误判断;详细验证范围见 docs/VALIDATION.md。

English

Adds local Tev1 0.8B and 4B alongside this-that-model 1.2 and Jev cloud, selectable per application. Candidate badges are exactly ✦ Jev, ✦ TT, and ✦ Tev.

Each model now has an independent 0.3–10 second timeout with save/reset controls. Defaults: 0.6s for Jev, TT and Tev 0.8B; 2s for Tev 4B. The budget includes debounce and candidate sampling. Native candidates remain immediately selectable regardless of model latency or failure.

The original first choice remains first. Matching recommendations add only a badge; other genuine candidates move to slot 2 without duplicates. Switching invalidates old responses and waits for model release. Successful downloads reload the still-selected provider.

Tev runs through an isolated pinned local service; the system Ollama installation is untouched. No credentials, personal dictionaries, local settings, weights, or runtime binaries are published.

Source release for Apple Silicon / macOS 14+. Follow LLM_INSTALL.md. Chinese prediction quality varies by model; see docs/VALIDATION.md for measured results and validation limits.

Verification / 验证

341 backend tests, 168 real-Rime probes, native settings/lifecycle tests, build/signature, installed smoke, and actual settings-window save/switch/reset checks passed. Backend line coverage: 89.31%; native coordinator: 91%. Gitleaks and private-metadata checks passed. Fresh manual typing feedback is tracked separately from engine and settings validation.