<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>蓝队 :: 标签 :: x7peeps</title><link>https://blog.x7peeps.com/tags/%E8%93%9D%E9%98%9F/index.html</link><description/><generator>Hugo</generator><language>zh-CN</language><lastBuildDate>Sat, 14 Nov 2026 12:00:00 +0800</lastBuildDate><atom:link href="https://blog.x7peeps.com/tags/%E8%93%9D%E9%98%9F/index.xml" rel="self" type="application/rss+xml"/><item><title>停机命令失败之后：你以为停了，它还在跑</title><link>https://blog.x7peeps.com/%E5%AE%89%E5%85%A8/%E5%A8%81%E8%83%81%E6%83%85%E6%8A%A5/%E5%81%9C%E6%9C%BA%E5%91%BD%E4%BB%A4%E5%A4%B1%E8%B4%A5%E4%B9%8B%E5%90%8E%E4%BD%A0%E4%BB%A5%E4%B8%BA%E5%81%9C%E4%BA%86%E5%AE%83%E8%BF%98%E5%9C%A8%E8%B7%91/index.html</link><pubDate>Sat, 14 Nov 2026 12:00:00 +0800</pubDate><guid>https://blog.x7peeps.com/%E5%AE%89%E5%85%A8/%E5%A8%81%E8%83%81%E6%83%85%E6%8A%A5/%E5%81%9C%E6%9C%BA%E5%91%BD%E4%BB%A4%E5%A4%B1%E8%B4%A5%E4%B9%8B%E5%90%8E%E4%BD%A0%E4%BB%A5%E4%B8%BA%E5%81%9C%E4%BA%86%E5%AE%83%E8%BF%98%E5%9C%A8%E8%B7%91/index.html</guid><description>一台 Intel Mac 上，openclaw gateway stop 和 openclaw gateway stop --force 都返回同一个错误：
Gateway stop failed: ServiceInspectionError: Process ancestry could not be fully inspected. Use the Gateway update action for a managed handoff, or retry from an independent terminal without inherited service markers. 报告者是在 Terminal.app 里从 Spotlight 直接启动的登录 shell 里执行的，没有继承任何服务标记。命令给出的那条建议——换个独立终端重试——他本来就已经满足。--force 的文档写的是「Allow stop from a non-interactive shell」，它同样没绕过检查。</description></item><item><title>223 条失败记录：消息静默丢失</title><link>https://blog.x7peeps.com/%E5%AE%89%E5%85%A8/%E5%BA%94%E6%80%A5%E5%93%8D%E5%BA%94/223-%E6%9D%A1%E5%A4%B1%E8%B4%A5%E8%AE%B0%E5%BD%95%E6%B6%88%E6%81%AF%E9%9D%99%E9%BB%98%E4%B8%A2%E5%A4%B1/index.html</link><pubDate>Fri, 13 Nov 2026 23:00:00 +0800</pubDate><guid>https://blog.x7peeps.com/%E5%AE%89%E5%85%A8/%E5%BA%94%E6%80%A5%E5%93%8D%E5%BA%94/223-%E6%9D%A1%E5%A4%B1%E8%B4%A5%E8%AE%B0%E5%BD%95%E6%B6%88%E6%81%AF%E9%9D%99%E9%BB%98%E4%B8%A2%E5%A4%B1/index.html</guid><description>一个 OpenClaw 实例的 Telegram 外发队列里，223 条历史失败记录，lastError 全是同一句：Network request for 'sendMessage' failed!。耗时全部落在 7.4 到 9.3 秒之间，retry_count 等于 1，recovery_state 停在 send_attempt_started，然后永久 failed。</description></item><item><title>一条 issue 刷了 292 条评论：Qwen Code 主 CI 门禁三周持续失败的检测债</title><link>https://blog.x7peeps.com/%E5%AE%89%E5%85%A8/%E5%A8%81%E8%83%81%E6%83%85%E6%8A%A5/%E4%B8%80%E6%9D%A1-issue-%E5%88%B7%E4%BA%86-292-%E6%9D%A1%E8%AF%84%E8%AE%BAQwen-Code-%E4%B8%BB-CI-%E9%97%A8%E7%A6%81%E4%B8%89%E5%91%A8%E6%8C%81%E7%BB%AD%E5%A4%B1%E8%B4%A5%E7%9A%84%E6%A3%80%E6%B5%8B%E5%80%BA/index.html</link><pubDate>Thu, 12 Nov 2026 23:50:00 +0800</pubDate><guid>https://blog.x7peeps.com/%E5%AE%89%E5%85%A8/%E5%A8%81%E8%83%81%E6%83%85%E6%8A%A5/%E4%B8%80%E6%9D%A1-issue-%E5%88%B7%E4%BA%86-292-%E6%9D%A1%E8%AF%84%E8%AE%BAQwen-Code-%E4%B8%BB-CI-%E9%97%A8%E7%A6%81%E4%B8%89%E5%91%A8%E6%8C%81%E7%BB%AD%E5%A4%B1%E8%B4%A5%E7%9A%84%E6%A3%80%E6%B5%8B%E5%80%BA/index.html</guid><description>QwenLM/qwen-code 的 issue #14724 由官方机器人 qwen-code-dev-bot 于 2026 年 10 月 19 日创建，标题是"Main CI failed: Managed Agent gate — no test identified"，截至 2026 年 11 月 12 日仍处于 open 状态，最新更新时间就是 11 月 12 日。</description></item><item><title>凭据在沙箱里被悄悄丢弃：Copilot CLI 的两个配置与现实错位</title><link>https://blog.x7peeps.com/%E5%AE%89%E5%85%A8/%E5%A8%81%E8%83%81%E6%83%85%E6%8A%A5/%E5%87%AD%E6%8D%AE%E5%9C%A8%E6%B2%99%E7%AE%B1%E9%87%8C%E8%A2%AB%E6%82%84%E6%82%84%E4%B8%A2%E5%BC%83Copilot-CLI-%E7%9A%84%E4%B8%A4%E4%B8%AA%E9%85%8D%E7%BD%AE%E4%B8%8E%E7%8E%B0%E5%AE%9E%E9%94%99%E4%BD%8D/index.html</link><pubDate>Thu, 12 Nov 2026 01:35:00 +0800</pubDate><guid>https://blog.x7peeps.com/%E5%AE%89%E5%85%A8/%E5%A8%81%E8%83%81%E6%83%85%E6%8A%A5/%E5%87%AD%E6%8D%AE%E5%9C%A8%E6%B2%99%E7%AE%B1%E9%87%8C%E8%A2%AB%E6%82%84%E6%82%84%E4%B8%A2%E5%BC%83Copilot-CLI-%E7%9A%84%E4%B8%A4%E4%B8%AA%E9%85%8D%E7%BD%AE%E4%B8%8E%E7%8E%B0%E5%AE%9E%E9%94%99%E4%BD%8D/index.html</guid><description>凭据在沙箱里被悄悄丢弃：Copilot CLI 的两个配置与现实错位 先说清楚这两件事的性质：它们是 Copilot CLI 用户在本地跑沙箱时提交的缺陷报告，主体是使用者本人，没有第三方攻击者介入，也没有审批环节被绕过。后果是使用者自己的合法操作失败——Gradle 起不来、gh 命令 401。</description></item><item><title>Agent的兜底链漏了最温柔的那种失败：内容过滤收尾不触发任何重试钩子</title><link>https://blog.x7peeps.com/AI/08-%E5%AE%89%E5%85%A8%E4%B8%8EAI%E8%9E%8D%E5%90%88/Agent%E7%9A%84%E5%85%9C%E5%BA%95%E9%93%BE%E6%BC%8F%E4%BA%86%E6%9C%80%E6%B8%A9%E6%9F%94%E7%9A%84%E9%82%A3%E7%A7%8D%E5%A4%B1%E8%B4%A5%E5%86%85%E5%AE%B9%E8%BF%87%E6%BB%A4%E6%94%B6%E5%B0%BE%E4%B8%8D%E8%A7%A6%E5%8F%91%E4%BB%BB%E4%BD%95%E9%87%8D%E8%AF%95%E9%92%A9%E5%AD%90/index.html</link><pubDate>Mon, 02 Nov 2026 21:00:00 +0800</pubDate><guid>https://blog.x7peeps.com/AI/08-%E5%AE%89%E5%85%A8%E4%B8%8EAI%E8%9E%8D%E5%90%88/Agent%E7%9A%84%E5%85%9C%E5%BA%95%E9%93%BE%E6%BC%8F%E4%BA%86%E6%9C%80%E6%B8%A9%E6%9F%94%E7%9A%84%E9%82%A3%E7%A7%8D%E5%A4%B1%E8%B4%A5%E5%86%85%E5%AE%B9%E8%BF%87%E6%BB%A4%E6%94%B6%E5%B0%BE%E4%B8%8D%E8%A7%A6%E5%8F%91%E4%BB%BB%E4%BD%95%E9%87%8D%E8%AF%95%E9%92%A9%E5%AD%90/index.html</guid><description>做 Agent 运维的人大多搭过这种保险：主模型挂了，自动切备用模型。限流、5xx、超时、断连——这些" provider 出事了"的场景都测过，钩子都接得住。但有一种失败长得完全不像故障：模型正常地开始回复、正常地结束数据流，只是最后交出来的是一份空白，收尾标记写着"内容过滤"。</description></item><item><title>macOS 后台总有声音却找不到来源：用 CoreAudio 进程级探针揪出真凶</title><link>https://blog.x7peeps.com/%E5%AE%89%E5%85%A8/%E5%AE%9E%E6%88%98%E5%A4%8D%E7%9B%98/macOS%E5%90%8E%E5%8F%B0%E6%80%BB%E6%9C%89%E5%A3%B0%E9%9F%B3%E5%8D%B4%E6%89%BE%E4%B8%8D%E5%88%B0%E6%9D%A5%E6%BA%90%E7%94%A8CoreAudio%E8%BF%9B%E7%A8%8B%E7%BA%A7%E6%8E%A2%E9%92%88%E6%8F%AA%E5%87%BA%E7%9C%9F%E5%87%B6/index.html</link><pubDate>Sun, 18 Oct 2026 00:22:00 +0800</pubDate><guid>https://blog.x7peeps.com/%E5%AE%89%E5%85%A8/%E5%AE%9E%E6%88%98%E5%A4%8D%E7%9B%98/macOS%E5%90%8E%E5%8F%B0%E6%80%BB%E6%9C%89%E5%A3%B0%E9%9F%B3%E5%8D%B4%E6%89%BE%E4%B8%8D%E5%88%B0%E6%9D%A5%E6%BA%90%E7%94%A8CoreAudio%E8%BF%9B%E7%A8%8B%E7%BA%A7%E6%8E%A2%E9%92%88%E6%8F%AA%E5%87%BA%E7%9C%9F%E5%87%B6/index.html</guid><description>macOS 后台一直在出声，浏览器没有播放标签，音乐类 App 都停在暂停态，活动监视器帮不上忙——这是 Mac 用户偶尔会撞上的排障死角。今天这个真实案例的答案相当意外：声音来自微信的内嵌浏览器子进程 WeChatAppEx，它不出现在活动监视器的音频列，微信主进程也不显示任何播放状态。</description></item><item><title>AI agent 网关越跑越慢直到假死：三类劣化信号和监控缺口</title><link>https://blog.x7peeps.com/%E5%AE%89%E5%85%A8/%E5%BA%94%E6%80%A5%E5%93%8D%E5%BA%94/AI-agent%E7%BD%91%E5%85%B3%E8%B6%8A%E8%B7%91%E8%B6%8A%E6%85%A2%E7%9B%B4%E5%88%B0%E5%81%87%E6%AD%BB-%E4%B8%89%E7%B1%BB%E5%8A%A3%E5%8C%96%E4%BF%A1%E5%8F%B7%E5%92%8C%E7%9B%91%E6%8E%A7%E7%BC%BA%E5%8F%A3/index.html</link><pubDate>Thu, 15 Oct 2026 01:25:00 +0800</pubDate><guid>https://blog.x7peeps.com/%E5%AE%89%E5%85%A8/%E5%BA%94%E6%80%A5%E5%93%8D%E5%BA%94/AI-agent%E7%BD%91%E5%85%B3%E8%B6%8A%E8%B7%91%E8%B6%8A%E6%85%A2%E7%9B%B4%E5%88%B0%E5%81%87%E6%AD%BB-%E4%B8%89%E7%B1%BB%E5%8A%A3%E5%8C%96%E4%BF%A1%E5%8F%B7%E5%92%8C%E7%9B%91%E6%8E%A7%E7%BC%BA%E5%8F%A3/index.html</guid><description>一个开源自托管 agent 网关的用户做了一次教科书级的资源问题排查：单用户、轻负载的实例，RSS 从 2.5 GB 一路涨到 8-10 GB，60 到 90 分钟内触发内存压力告警，最终威胁 OOM。他排除了插件、排除了面板轮询、排除了厂商插件，冷重启后泄漏照旧——最后用堆剖析把问题定位到核心包里一个模型目录 worker。这是 OpenClaw #159662，2026 年 9 月末开出的 P0 级 issue。把它和同项目的另外两条问题（僵尸进程堆积、MCP 调用审批缺口）放在一起看，会得到一张对 AI agent 基础设施运维很有用的"劣化信号地图"：长驻 agent 服务出问题，往往不是崩，而是慢、拖、漏。</description></item></channel></rss>