Repository navigation
fix(openclaw): honour logLevel and logSummaryIntervalMs - #5532
Merged
Merged
Conversation
getPluginConfig never copied either field, so the logger always ran at info with a 5-minute summary whatever the user set. On top of that, debugEnabled used `debug ?? logLevel === "debug"`, but debug is always a boolean after getPluginConfig, so logLevel could never turn on debug lines. The new test also checks that every manifest default survives getPluginConfig, which catches the next field the whitelist forgets.
nicoloboschi
force-pushed
the
fix/openclaw-loglevel-debug
branch
from
October 12, 2026 11:03
1efb411 to
cf788e8
Compare
This was referenced Oct 14, 2026
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Found while testing the openclaw fixes on a real gateway:
logLevel: "debug"produced no debug lines.getPluginConfignever copiedlogLevelorlogSummaryIntervalMs, so the logger always ran atinfowith a 5-minute summary, whatever the user set.debugEnabled = debug ?? logLevel === "debug"never reachedlogLevel, becausedebugis always a boolean aftergetPluginConfig.Tests:
log-level.test.tschecks thatlogLevel: "debug"alone turns on debug lines, and that every manifest default survivesgetPluginConfig. The second test catches the next field the whitelist forgets. Both fail onmain.Verified on real OpenClaw 2026.10.2: with only
logLevel: "debug"set, the gateway log now shows the plugin's debug lines (Registering agent hooks...). Onmainit showed none.