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.
36 lines
1.1 KiB
TypeScript
36 lines
1.1 KiB
TypeScript
import { AsyncLocalStorage } from 'async_hooks';
|
|
|
|
interface RequestStore {
|
|
id: number;
|
|
}
|
|
|
|
const storage = new AsyncLocalStorage<RequestStore>();
|
|
let counter = 0;
|
|
|
|
/**
|
|
* Allocate the next per-process request id (monotonic). Wraps via uint32 so
|
|
* it never overflows to a non-integer; `0` is skipped so "no id" stays
|
|
* unambiguous.
|
|
*/
|
|
export function nextRequestId(): number {
|
|
counter = (counter + 1) >>> 0;
|
|
if (counter === 0) counter = 1;
|
|
return counter;
|
|
}
|
|
|
|
/**
|
|
* Run `fn` with `id` bound as the ambient request id for the entire async
|
|
* chain it spawns. Any logger call anywhere in that chain — across packages,
|
|
* across awaits — picks it up via {@link currentRequestId} with no signature
|
|
* threading. Used by the OneBot action handler to correlate a request's whole
|
|
* journey (entry → outbound packets → exit) under one `[req#N]` tag.
|
|
*/
|
|
export function runWithRequestId<T>(id: number, fn: () => T): T {
|
|
return storage.run({ id }, fn);
|
|
}
|
|
|
|
/** The request id bound to the current async context, or undefined outside one. */
|
|
export function currentRequestId(): number | undefined {
|
|
return storage.getStore()?.id;
|
|
}
|