Mac source-built Home skips the model provider when llama-server has no checksum, and the log hides why
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
研究方向
Start by reading the failure path at setup.rs:2237-2251 and server_infra.rs:1034, 1135, then trace how the missing llama-server checksum affects the local engine bundle and provider startup. Check scripts/build-and-setup-source-home.sh and the release integrity checks for the source Home setup. Done means the startup reason appears in logs and System, hosted model startup works without a local engine, and an installed Mac Home test covers that case.
由索引模型根據 Issue 內容生成。
描述
A Mac Home built from source with the default setup (scripts/build-and-setup-source-home.sh without SETUP_SOURCE_HOME_INSTALL_LLAMA_SERVER=1) leaves the llama-server darwin-arm64 entry in components.json with no checksum.
- What happens: the Runtime can't resolve the local engine's sandbox bundle (
setup.rs:2237-2251,local_model_engine_confinement_bundle), so model-provider startup fails (server_infra.rs:1034). - Why nobody can tell: the gateway logs only "Skipping model-provider because startup failed"; the error is dropped at
server_infra.rs:1135. The Assistant and hosted models are then unavailable with no stated reason. - Packaged releases are not affected (from a code read): release preparation fills the darwin checksum, and release checks refuse a missing one (
prepare-release-platform.sh:293,310-330,components-release-integrity-check.py:203-214).
Found while preparing the #85 installed proof (20 Oct).
Done means
- The startup failure names its reason in the log and in System.
- A Mac source Home without a local engine still starts the model provider, so hosted models work. Test: a source Home built with the default setup reaches
model-provider capsule from …. - A test covers an installed Mac Home without local AI starting the model provider.
- 主要語言
- Rust
- 星號
- 6
- 分支
- 2
- 平均合併
- 1 天 3 小時
- 30 天內合併 PR
- 42
環境準備
這個專案沒有提供開發容器、Dockerfile 或貢獻指南，環境需要你自己搭建：先看它的 README，通用步驟見我們的新手貢獻指南。
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
elastos/elastos-runtime 的其他 Issue
-
難度 2/5 1-3 小時 新手友好度 72/100
elastos/elastos-runtime#563 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 76/100
elastos/elastos-runtime#508 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 72/100
elastos/elastos-runtime#436 · 1 則留言 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 78/100
elastos/elastos-runtime#427 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 78/100
elastos/elastos-runtime#405 ·
維護者通常 1 天內回覆
查看 elastos/elastos-runtime 的全部 Issue
相似的 Issue
-
難度 2/5 1-3 小時 新手友好度 75/100
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 68/100
antiguru/interrexx#213 · 2 則留言 ·
維護者通常 1 天內回覆
-
bug
難度 2/5 1-3 小時 新手友好度 78/100
維護者通常 1 天內回覆
-
bug CLI
難度 2/5 1-3 小時 新手友好度 77/100
HigherOrderCO/Bend#2120 ·
-
難度 2/5 1-3 小時 新手友好度 66/100
KNXBench-Labs/KNXBench#47 ·