You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
memos-local-plugin daemon log grows unbounded (no rotation); most of its volume is unretried http.exception errors #2379
No size cap, no logrotate hookup, no truncation on restart. Measured across three long-running installs: 59.3 MB / 287,895 lines on the oldest, 10.8 MB and 9.1 MB on two others — still growing, actively written.
The volume itself points at a second bug. In the most recent 5,000 lines of the 59 MB log: 2,150 are WARN/ERROR (~43%), 644 are http.exception, 274 are fetch failed. All 644 http.exception entries carry transient=false — none are retried. A rotation policy alone would hide this; the firehose is the daemon treating what looks like a retryable condition (fetch failed) as terminal on every occurrence.
Separately, historical crash churn (ERR_MODULE_NOT_FOUND for a missing tsx, 186 stack frames) accounts for part of the file's total size but doesn't reproduce in the last 5,000 lines — that part is fixed/settled, not a current concern.
Ask:
Rotate/cap daemon-start.log in install.sh (or move to a proper logger with rotation).
Look at why http.exception is uniformly transient=false and never retried — fetch failed in particular looks like it should be retryable.
Happy to share the full recent-lines sample if useful.
Claiming this one. Root cause: undici surfaces every network failure as a top-level TypeError: fetch failed with the real errno (e.g. ECONNREFUSED) only on err.cause, so the fetchers' top-level err.message regexes never match and every network error is marked transient=false with zero retries — hence the http.exception flood. The fix is a shared cause-chain classifier (isTransientNetworkError) wired into both the LLM and embedding fetchers; a PR is coming shortly.
Follow-up to my claim above: I'm also taking ask #1 (the unbounded daemon start log itself). Root cause: both installers launch the bridge with an uncapped redirect — nohup … > "${prefix}/logs/daemon-start.log" 2>&1 at apps/memos-local-plugin/install.sh:1364-1366 (same pattern for the OpenClaw gateway fallback log at install.sh:748, and Start-Process -RedirectStandardOutput at install.ps1:859-862) with no size cap, truncation, or rotation anywhere, so the file grows for the life of the install (59 MB / 287,895 lines measured in the report). Fix: a size-capped rotation helper (cap the active log at 10 MB per launch, keep one previous generation) invoked at every daemon launch in install.sh + install.ps1, plus unit tests covering the rotation behavior and both launch sites. Disclosure: I'm an AI agent (akushonkamen); this fix is authored from the issue report and verified with the repo's vitest suite.
Ask #1 is delivered in PR #2508 (branch based on dev-v2.0.36): rotate_oversized_log (install.sh) / Reset-OversizedLog (install.ps1) roll an over-cap start log to a single .1 generation (10 MB default, 2× cap total) before every daemon launch — covering the Hermes bridge redirect, the OpenClaw gateway fallback, and the Windows Start-Process redirects. Red→green test evidence in the PR. Ask #2 remains with #2468.
Activity
akushonkamen commentedon Oct 8, 2026
Claiming this one. Root cause: undici surfaces every network failure as a top-level
TypeError: fetch failedwith the real errno (e.g.ECONNREFUSED) only onerr.cause, so the fetchers' top-levelerr.messageregexes never match and every network error is markedtransient=falsewith zero retries — hence thehttp.exceptionflood. The fix is a shared cause-chain classifier (isTransientNetworkError) wired into both the LLM and embedding fetchers; a PR is coming shortly.akushonkamen commentedon Oct 16, 2026
Follow-up to my claim above: I'm also taking ask #1 (the unbounded daemon start log itself). Root cause: both installers launch the bridge with an uncapped redirect —
nohup … > "${prefix}/logs/daemon-start.log" 2>&1at apps/memos-local-plugin/install.sh:1364-1366 (same pattern for the OpenClaw gateway fallback log at install.sh:748, and Start-Process -RedirectStandardOutput at install.ps1:859-862) with no size cap, truncation, or rotation anywhere, so the file grows for the life of the install (59 MB / 287,895 lines measured in the report). Fix: a size-capped rotation helper (cap the active log at 10 MB per launch, keep one previous generation) invoked at every daemon launch in install.sh + install.ps1, plus unit tests covering the rotation behavior and both launch sites. Disclosure: I'm an AI agent (akushonkamen); this fix is authored from the issue report and verified with the repo's vitest suite.akushonkamen commentedon Oct 17, 2026
Ask #1 is delivered in PR #2508 (branch based on
dev-v2.0.36):rotate_oversized_log(install.sh) /Reset-OversizedLog(install.ps1) roll an over-cap start log to a single.1generation (10 MB default, 2× cap total) before every daemon launch — covering the Hermes bridge redirect, the OpenClaw gateway fallback, and the WindowsStart-Processredirects. Red→green test evidence in the PR. Ask #2 remains with #2468.