Config changes are saved to a hardcoded relative "config.ron", not the config path podd was launched with

未关闭 适合新手
#26 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
67/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
冷清
技术栈
rust
领域
backend

调研方向

阅读 crates/podd-core/src/config/mod.rs 和 crates/podd-core/src/config/mqtt.rs,然后追踪 main.rs 如何将 CLI 配置路径传给 Config::load。更新保存路径,使其使用加载时使用的路径;验证 MQTT 设置操作会持久化到该文件,并检查相关测试,或在需要时补充测试覆盖。

由索引模型根据 Issue 内容生成。

描述

bug

Config::save is only ever called with the module constant CONFIG_FILE = "config.ron" (crates/podd-core/src/config/mod.rs:18, used at crates/podd-core/src/config/mqtt.rs:292). But the daemon loads its config from an arbitrary path — main.rs passes the first CLI arg (default ./config.ron) through to Config::load (crates/podd-core/src/lib.rs:140). So when podd is started with any config path other than a file literally named config.ron in the process CWD, every MQTT set_ action (away_mode, prime, profile, presence) persists to ./config.ron in the working directory instead of the file that was loaded. On next boot the loaded file is unchanged and the user's edits silently vanish. save() should take the same path load() used.

This bites the clean-room OS unit today: os/package/podd/podd.service runs ExecStart=/usr/bin/podd /data/podd/config.ron with WorkingDirectory=/data, so runtime edits land in /data/config.ron and are lost on restart. install/podd.service only avoids it by accident because its WorkingDirectory happens to match its config location.


Filed from a repo-wide code audit (working tree at bcad746).

主要语言
Rust
星标
0
派生
0
PR 合并指标
30 天内没有已合并 PR

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

GoogleBot42/podd 的其他 Issue

查看 GoogleBot42/podd 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。