mirror of
https://github.com/hanzoai/bot.git
synced 2026-10-30 17:24:26 +00:00
zeekay
acaeda400a
Three coordinated things:
1. Resolve the committed upstream/main merge conflicts. 94 files were
sitting with raw <<<<<<< HEAD ... >>>>>>> upstream/main blocks. Every
conflict had HanzoBot/Bot on HEAD and OpenClaw on upstream. Resolved
by keeping HEAD everywhere — 540 conflict blocks.
2. Rewrite remaining OpenClaw text refs.
OPENCLAW → HANZO_BOT
OpenClaw → HanzoBot (PascalCase type identifiers)
openclaw → bot (codebase convention — botToken,
botUsername etc.; avoids invalid
hyphenated JS identifiers)
openclaw[_]/openclaw[A-Z] → bot[_]/bot[A-Z] (compound)
ai.openclaw.x → ai.hanzo.bot.x (JVM package path)
3. Delete or rename openclaw-named file paths (116 of them). Dead
duplicates with a Bot-named canonical from the partial migration:
deleted. Otherwise renamed.
ai/openclaw/** → deleted (ai/hanzo/bot/** canonical)
Sources/OpenClaw*/ → deleted (Sources/Bot* canonical)
Tests/OpenClawIPCTests/ → deleted (Tests/BotIPCTests canonical)
OpenClawKit/ → deleted (BotKit canonical)
openclaw-tools.*.ts → deleted (bot-tools.*.ts canonical)
openclaw-root.ts etc. → deleted (bot-root.ts canonical)
types.openclaw.ts → deleted (types.bot.ts canonical)
extensions/*/openclaw.plugin.json → renamed hanzo-bot.plugin.json
docs/start/openclaw.md → renamed hanzo-bot.md (+ zh-CN)
docs/assets/openclaw-*.png, whatsapp-openclaw*.jpg → deleted
scripts/.../openclaw-* → deleted (bot/hanzo-bot parallels)
openclaw.mjs → deleted (hanzo-bot.mjs is package.bin)
Then patched 65 broken JS/TS import strings where hanzo-bot had ended
up inside an import path ('./types.hanzo-bot.js' → './types.bot.js'
etc., since the on-disk filename uses the brand-neutral bot- prefix).
Pre-existing lint debt cleaned up to get oxlint --type-aware to 0/0:
removed the dead i18n test that referenced a path no longer existing;
defined the missing DIDConfig and WalletConfig types in types.base.ts
(they were imported but never declared); dropped unused imports;
collapsed redundant type assertion and a tautological meta.bot lookup
that the openclaw→bot rename made redundant.
The a2ui.bundle.js generated artifact is kept at its pre-rebrand
contents — it gets regenerated by 'pnpm canvas:a2ui:bundle' from
sources I cannot rebuild in this commit; the source side is clean.
Verified: 0 occurrences of openclaw (case-insensitive) in tree source
content, 0 file or directory paths with openclaw in the name; oxlint
--type-aware src test reports 0/0.
2.2 KiB
2.2 KiB
read_when, summary, title, x-i18n
| read_when | summary | title | x-i18n | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
用于定向调试日志的诊断标志 | 诊断标志 |
|
诊断标志
诊断标志让你可以启用定向调试日志，而无需在所有地方开启详细日志。标志是可选启用的，除非子系统检查它们，否则不会生效。
工作原理
- 标志是字符串（不区分大小写）。
- 你可以在配置中或通过环境变量覆盖来启用标志。
- 支持通配符：
telegram.*匹配telegram.http*启用所有标志
通过配置启用
{
"diagnostics": {
"flags": ["telegram.http"]
}
}
多个标志：
{
"diagnostics": {
"flags": ["telegram.http", "gateway.*"]
}
}
更改标志后重启 Gateway 网关。
环境变量覆盖（一次性）
BOT_DIAGNOSTICS=telegram.http,telegram.payload
禁用所有标志：
BOT_DIAGNOSTICS=0
日志存储位置
标志将日志输出到标准诊断日志文件。默认位置：
/tmp/hanzo-bot/hanzo-bot-YYYY-MM-DD.log
如果你设置了 logging.file，则使用该路径。日志为 JSONL 格式（每行一个 JSON 对象）。脱敏仍然根据 logging.redactSensitive 应用。
提取日志
选择最新的日志文件：
ls -t /tmp/hanzo-bot/hanzo-bot-*.log | head -n 1
过滤 Telegram HTTP 诊断：
rg "telegram http error" /tmp/hanzo-bot/hanzo-bot-*.log
或在复现时使用 tail：
tail -f /tmp/hanzo-bot/hanzo-bot-$(date +%F).log | rg "telegram http error"
对于远程 Gateway 网关，你也可以使用 hanzo-bot logs --follow（参见 /cli/logs）。
注意事项
- 如果
logging.level设置为高于warn，这些日志可能会被抑制。默认的info级别即可。 - 标志可以安全地保持启用状态；它们只影响特定子系统的日志量。
- 使用 /logging 更改日志目标、级别和脱敏设置。