operator-drive-adapter never starts: Runtime sends allowed_paths, the adapter accepts only base_path
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
Read the startup caller in elastos/crates/elastos-server/src/server_infra.rs, the BridgeProviderConfig serialization in elastos/crates/elastos-runtime/src/provider/bridge.rs, and the strict parser in capsules/operator-drive-adapter/src/main.rs. Reproduce the refusal with the current wire request, then trace how the other providers preserve path rules. Done means a regression starts the adapter through the Runtime bridge, succeeds at Init, and serves an allowed operation.
由索引模型根据 Issue 内容生成。
描述
Every Home start logs Failed to spawn operator-drive-adapter: provider init failed: invalid_request: unknown field 'allowed_paths', expected 'base_path' or 'extra'.
The Runtime's operator drive startup uses the shared BridgeProviderConfig. ProviderBridge serializes this struct into the Init request, including the default empty allowed_paths, read_only, and encryption_key fields. The adapter accepts only base_path and extra and rejects unknown fields. Main observed the refusal after binary verification on the packaged Jetson trial. Root checked the same caller, wire fields and strict parser in v2.0.0 and 30b166b05. Startup caller · Bridge config · Adapter parser
Pre-existing: the same code is in 2.0.0 (v2.0.0) and unchanged in 2.0.1-rc.1 (30b166b05); seen on the rc.1 Jetson test Home (7 Nov). Not a 2.0.1 regression.
Main owns the fix when this issue reaches the implementation lane. Align the operator drive Init request with the adapter's config. Keep strict decoding and preserve the path rules of the other providers. Add a regression that starts the adapter through the real Runtime bridge and verifies Init succeeds, then proves that the adapter can serve an allowed operation. The current wire request should reproduce the startup refusal in that regression.
- 主要语言
- 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
-
bug good first issue help wanted linux macos testing
难度 2/5 1-3 小时 新手友好度 85/100
维护者通常 1 天内回复
-
area: app type: test
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
bug priority: medium
难度 2/5 1-3 小时 新手友好度 78/100
storytold/photocraft#12706 · 1 条评论 ·
维护者通常 1 天内回复
-
bug priority-low to-agent
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 1 天内回复
-
examples/dca and limit-order: swap always fails on the real Soroswap router (deadline equals now)未关闭
难度 2/5 1-3 小时 新手友好度 76/100
sorocon-labs/sorocron#172 ·
维护者通常 1 天内回复