DrSmoothl 15e4e261c5 feat(log): memory-only trace level + request correlation + chokepoint tracing
Debugging from user-supplied logs was impossible: a successful action left
one terse, over-summarized debug line and nothing about what it sent QQ or
what QQ returned. Add full-chain tracing that stays off disk so it scales to
hundreds of groups.

common:
- New `trace` level (below debug). Never written to file — it lives only in
  an in-memory ring + the WebUI stream, so the high-volume full chain costs no
  disk. `emit` early-returns for trace before format/render (and before any
  lazy producer) when trace isn't active → ~free at the default level.
- Dedicated O(1) circular ring for trace (default 5000, SNOWLUMA_TRACE_BUFFER),
  separate from the normal 1000-entry buffer (also switched off array .shift);
  getRecentLogs merges both by id.
- request-context.ts: AsyncLocalStorage request id. The logger auto-stamps
  `[req#N]` on every line in a request's async chain — across packages, zero
  signature threading — and records it on the entry.
- log-summary.renderParamsVerbose: deep render of params (nested structure,
  per-string cap, total budget, token/password/secret redaction).

chokepoints (auto-cover every action without touching 100+ handlers):
- onebot api-handler: wrap each action in a request id (only when trace is
  live); trace the full params on entry and status+elapsed on exit; the terse
  debug breadcrumb still persists to file, failures still warn.
- core bridge.sendRawPacket: trace on success (cmd, sizes, elapsed); warn on
  errorCode!=0 / no response (cmd, code, message) so disk keeps real problems.
- protocol highway: fold the bare console.log lines into the logger (trace).

webui: trace as the lowest filterable level; render the `[req#N]` tag and let
search match it. Server needs no change — LOG_LEVELS, getRecentLogs and the
SSE stream carry it through.
2026-06-02 21:01:19 +08:00
2026-05-30 16:06:29 +08:00
2026-05-03 14:02:29 +08:00
2026-06-01 16:21:54 +08:00
2026-05-30 16:06:29 +08:00

SnowLuma

Next Remote Protocol Framework.

Release Build NPM Stars

Releases · Issues · QQ 群 · Telegram


SnowLuma 是一个基于 TypeScript 的协议转换框架,旨在为 QQ 客户端提供 OneBot v11 标准接口,支持 WebSocket/HTTP 适配、多账号并行及 WebUI 管理。

特性

  • OneBot v11 兼容:支持文本、音视频、Markdown、JSON 等消息格式。
  • 高性能架构:TypeScript 全栈,基于 pnpm monorepo 管理,核心逻辑分离。
  • 现代化管理:内置 WebUI 面板,支持实时日志、密码热更、多账号管理。
  • 多适配器支持:WebSocket (Server/Client)、HTTP (Server/Post)。
  • 数据持久化:使用 SQLite 存储好友、群组等关系数据。

快速开始

  1. 从 Releases 下载最新发布包并解压。
  2. 运行 ./launcher.bat (Windows) 或 ./launcher.sh (Linux)。
  3. 访问 http://localhost:5099 (初始账号 admin,密码见控制台输出)。

鸣谢

参考了 LagrangeV2 的协议定义与 NapCatQQ 的实现思路。


S
Description
No description provided
Readme
64 MiB
Languages
TypeScript 98.9%
CSS 0.5%
JavaScript 0.5%