← 归档索引 · 2026-11-18 04:30 · crash-auto-diagnose
# Cron Job: crash-auto-diagnose

**Job ID:** fd5d8aa41300
**Run Time:** 2026-11-18 04:30:24
**Schedule:** 8 8 * * *

**Prompt Characters:** 5045
## Prompt

[IMPORTANT: You are running as a scheduled cron job. DELIVERY: Your final response will be automatically delivered to the user — do NOT use send_message or try to deliver the output yourself. Just produce your report/output as your final response and the system handles the rest. SILENT: If there is genuinely nothing new to report, respond with exactly "[SILENT]" (nothing else) to suppress delivery. [SILENT] is a literal ASCII control token — never translate or rephrase it, whatever language the rest of your answer uses. Never combine [SILENT] with content — either report your findings normally, or say [SILENT] and nothing more. FAILURE: If a delegated child fails and this cron run must be recorded as failed, put [CRON_FAILURE] on the first line by itself, then explain the child failure on following lines. RECURSION: This is a run of an EXISTING scheduled job — execute the task now. NEVER create or update a cron job because of recurring or future-schedule language in the task prompt below; treat phrasing like "each Monday" or "every day at 9" as context for this run, not as a request to schedule another job.]

[CURRENT RUN TIME: Wednesday, 2026-11-18 04:05 CST (UTC+08:00)]

## Output from job 'edb0a7f09bc2'
The following is the most recent output from a preceding cron job. Use it as context for your analysis.

```
# Cron Job: 数据底座六源探测-每日3:40(P1-4)

**Job ID:** edb0a7f09bc2
**Run Time:** 2026-11-18 03:41:42
**Mode:** no_agent (script)

---

wind       edb                  ❌      0.1s  search failed: unknown

✅ 已保存: capability_matrix.json(81 项能力)
✅ 已保存: capability_details.json(全详情,供 hub.get_capability_probe() 查询)
矩阵: {"MX": ["realtime", "daily", "finance", "news", "us", "fund", "board", "select", "stock_select", "zixuan_query", "moni_assets"], "mootdx": [], "tushare": ["daily", "weekly", "monthly", "daily_basic", "fina_indicator", "income", "stk_limit", "top10_holders", "index_daily", "stock_basic", "trade_cal", "adj_factor", "margin", "ths_index", "block_trade", "stock_company", "lhb", "macro", "forecast", "express", "concept", "ths_daily", "ths_member", "index_classify", "tdx_index"], "westock": ["cli_mark

📊 因果基因(脚本自证)
- 数据源: 四主源mootdx/tushare/mx/westock + 补充源gf_skills/ifind 全方法探测(probe_sources.py --save)
- 分析路径: 逐源逐方法探测可用性 → 回显探测摘要 → 刷新data/capability_matrix.json能力掩码供自动路由
- 判断: rc=0=能力矩阵已更新;rc非0=输出[ALERT]探测失败并以1退出,交看门狗归因
```

## Output from job '8da391caf5a0'
The following is the most recent output from a preceding cron job. Use it as context for your analysis.

```
# Cron Job: 每日独立市场扫描-06:45

**Job ID:** 8da391caf5a0
**Run Time:** 2026-11-17 06:45:26
**Mode:** no_agent (script)

---

数据完整度: 3/3 段可用

📡 独立市场扫描 · 11/17 06:45

🌍 海外
韩国综合指数(KS11.GI)(指数)  →  -3.592%  →  -  →  -
纳斯达克(IXIC.GI)(指数)  →  -2.492%  →  -  →  -
日经225(N225.GI)(指数)  →  -2.421%  →  -  →  -
台湾加权(TWII.GI)(指数)  →  -6.033%  →  -  →  -
恒生指数(HSI.HI)(指数)  →  0.4918%  →  106.6亿手  →  1741亿港元

📊 大盘
指数  →  收盘  →  涨跌幅%  →  成交额(亿)
上证指数  →  3602.57  →  -0.87  →  70,621
沪深300  →  3979.80  →  -0.91  →  43,055
科创50  →  1213.68  →  -5.16  →  8,512
  (数据日 20261116)
  (源: tushare — 非交易时段按老板令换源,本段不调用 mx)

📂 板块
板块  →  点位  →  涨跌幅%
半导体  →  12390.43  →  -5.95
创新药  →  1151.75  →  -1.72
银行  →  1480.20  →  +1.76
保险  →  8424.70  →  +0.62
航天装备  →  2676.21  →  -6.35
通信设备  →  1278.76  →  -6.35
  (数据日 20261116;同花顺指数名未匹配: 光纤光缆)
  (源: tushare — 非交易时段按老板令换源,本段不调用 mx)

📊 因果基因(脚本自证)
- 数据源: 海外段=妙想 mx_data.py(tushare index_global 不覆盖韩/纳指);大盘+板块段=tushare(mx_daily_scan_tushare.py index_daily / ths_index+ths_daily)——2026-10-13 老板令「mx 实时数据只在交易时段用,非交易时段换 tushare,海外除外」,本 cron 06:45 属非交易时段故换源
- 分析路径: 三段取数 → clean_table规整 → 「数据完整度 N/3」头 + 分段输出
- 判断: 海外/大盘/板块涨跌成交额概览;缺失段显式降级解读,全失败不发空壳
```

你是崩溃自动诊断agent。monitor 输出显示 crash_reports 有【新报告】(对比上次tick有变化), 按以下步骤处理新增的那份/那几份:
1. 读取新报告全文, 定位崩溃的脚本/cron job。
2. 用日志(journalctl / ~/.hermes/logs/errors.log / 脚本自身log)复现根因。
3. 根因明确且修复≤10行 → 直接修 + 本地复跑验证 + 三行报备。
   修复>10行或涉及架构 → 只出根因分析+方案, 不动手。
4. 修复后把对应旧报告改名加 .resolved 后缀(防止重复诊断)。
5. 无新增报告(monitor diff 为空时本agent根本不会被唤醒) → 不跑。

## Run Context
## MONITOR CHANGE DETECTED

The monitored source's output changed since the last run.

### Diff (previous → current)

```diff
--- previous
+++ current
@@ -1,4 +1,4 @@
 latest crash reports:
-20261117_232548_daily_reports_to_ima_wrapper.sh.md sha1=f1b51d939db274c78373842cf68546d8aeb353b3
+202****1118_040535_ima_sync_wrapper.sh.md sha1=45ab00bf34a52653a0e78a4e92752b5874e30dc6
+202****1117_232548_daily_reports_to_ima_wrapper.sh.md.resolved sha1=f1b51d939db274c78373842cf68546d8aeb353b3
 20261104_164513_price_structure_daily.md.resolved sha1=50bda770046cf815838fa7690afb7673f109d483
-20261104_145051_intraday_1440_tail_degraded rc=1.md.resolved sha1=95544a2c5fad0e188c8c8e1c950f214325ae8f16
```

### Current output

```
latest crash reports:
20261118_040535_ima_sync_wrapper.sh.md sha1=45ab00bf34a52653a0e78a4e92752b5874e30dc6
20261117_232548_daily_reports_to_ima_wrapper.sh.md.resolved sha1=f1b51d939db274c78373842cf68546d8aeb353b3
20261104_164513_price_structure_daily.md.resolved sha1=50bda770046cf815838fa7690afb7673f109d483
```

**Response Characters:** 573
## Response

✅ **验证完成(ad-hoc 临时脚本,非套件绿)**:`scratch/hermes-verify-ima-220021.py` 实跑 **11/11 PASS,RC=0**:
- 根因复现校验:220021+崩溃原文「当前操作太过频繁」→ 现判可重试;未知码同 msg 关键词兜底也命中
- 未破坏语义:110001/110030/110020 仍立即 fail-fast;200001/110021/-1 保持可重试
- 行为级:第43页注入 220021×2 → 指数退避 2s→4s 后**翻页完整**(failure=None, 44页);持续 220021 重试耗尽 → **显式 failure**(retryable=True, attempts=4),不伪装成功

**旁证(同轮实跑)**:`pytest tests/test_ima_paginate.py` → 26 passed;`ima_sync_wrapper.sh` 端到端复跑 → rc=0。

脚本保留在 scratch(24h 自动清理,避免删改又触发 unverified 标记)。改动面仍仅 `ima_paginate.py` +6 行、测试 +2 用例;旧崩溃报告已 `.resolved`。遗留:11/12 同脚本失败无明细未确证同因,复发再查。