Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

[Bug]: fw doctor says `resolver-loop.timer is installed but inactive` on hosts where it is not installed (systemd 245)

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

还没有人认领这个 Issue。

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
75/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
活跃
技术栈
linux, shell
领域
cli, devops

调研方向

从bin/fw:4529开始,检查fw doctor如何确认resolver-loop.timer是否已安装。在 systemd 245 上重现报告中的行为,或使用 issue 中的命令输出了解为什么仅凭退出代码不足以判断。若不存在匹配的单元文件,且fw doctor报告该单元未安装,则任务完成。

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

描述

area:cli bug severity:low status:fixed-on-bleeding-edge triaged
Bug Description

bin/fw:4529 decides that the unit exists from the exit code of systemctl list-unit-files resolver-loop.timer. On systemd 245 this command exits 0 when nothing matches:

$ systemctl list-unit-files resolver-loop.timer; echo "code $?"
UNIT FILE STATE VENDOR PRESET

0 unit files listed.
code 0

So the not installed on this host branch is never reached, and fw doctor prints INFO systemd resolver-loop.timer is installed but inactive.

Steps to Reproduce
  1. Host with systemd 245 (Ubuntu 20.04) and no resolver-loop.timer (system or user).
  2. systemctl list-unit-files resolver-loop.timer; echo $? prints 0 unit files listed. and 0.
  3. fw doctor, section Autonomous Dispatch: INFO systemd resolver-loop.timer is installed but inactive.
Expected Behavior

INFO systemd resolver-loop.timer not installed on this host. A test that does not rely on the exit code, for example systemctl list-unit-files resolver-loop.timer --no-legend | grep -q resolver-loop.timer.

Actual Behavior

INFO systemd resolver-loop.timer is installed but inactive, which sends the operator looking for a unit that does not exist.

fw doctor output

AI Agent

Claude Code

Operating System

Linux

Additional Context

1.8.11 (e42aa41bf), vendored consumer, Linux (Ubuntu 20.04, systemd 245), Claude Code. Not checked: newer systemd versions may return non-zero when nothing matches, which would explain why this is not seen everywhere. Low severity (INFO line).

主要语言
Shell
星标
16
派生
6
平均合并
6 小时 24 分钟
30 天内合并 PR
5

环境准备

  • 提供 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

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

DimitriGeelen/agentic-engineering-framework 的其他 Issue

查看 DimitriGeelen/agentic-engineering-framework 的全部 Issue

相似的 Issue

更多 Shell/Bash Issue

把新 issue 发到你的邮箱

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