Skip to content

fix(helm): default verbosity to info in chart values - #4439

Merged
reinkrul merged 4 commits into
masterfrom
fix/chart-default-verbosity
Aug 18, 2026
Merged

fix(helm): default verbosity to info in chart values#4439
reinkrul merged 4 commits into
masterfrom
fix/chart-default-verbosity

Conversation

@stevenvegt

Copy link
Copy Markdown
Member

Changes the Helm chart's default verbosity from debug to info, matching the node's own code default (core/server_config.go). Bumps the chart version to 0.0.9.

Debug verbosity produces far more log output than a production deployment needs, and a lower default verbosity reduces the impact of anything that logs more than it should. The node itself already defaults to info; only the chart deviated.

Operators who want debug logging can still set nuts.config.verbosity: debug in their own values.

The chart shipped verbosity: debug while the node's own default is
info (core/server_config.go). Debug verbosity produces far more log
output than needed in production and increases the impact of any
log-hygiene issue, so the chart now matches the code default.

Assisted-by: AI
@stevenvegt
stevenvegt force-pushed the fix/chart-default-verbosity branch from 9739238 to a2a799f Compare July 30, 2026 12:51
@qltysh

qltysh Bot commented Jul 30, 2026

Copy link
Copy Markdown
Contributor

Qlty


Coverage Impact

This PR will not change total coverage.

🚦 See full report on Qlty Cloud »

🛟 Help
  • Diff Coverage: Coverage for added or modified lines of code (excludes deleted files). Learn more.

  • Total Coverage: Coverage for the whole repository, calculated as the sum of all File Coverage. Learn more.

  • File Coverage: Covered Lines divided by Covered Lines plus Missed Lines. (Excludes non-executable lines including blank lines and comments.)

    • Indirect Changes: Changes to File Coverage for files that were not modified in this PR. Learn more.

…erbosity

; Conflicts:
;	docs/pages/release_notes.rst
stevenvegt added a commit that referenced this pull request Aug 17, 2026
assertJaegerTrace only retried while the trace was entirely absent
from Jaeger. Each node exports spans in batches on its own schedule
(5s default), so the first query after a flow often finds a partial
trace containing only one node's spans, which failed the assertion
immediately. Missing services or spans are now retried like a missing
trace, up to 10 attempts with 1s sleeps.

The gossip test gave propagation of 81 transactions across 4 nodes
only 10 seconds, the heaviest propagation assertion in the suite on
the same budget as tests waiting for at most 41 transactions. Slow CI
runners regularly miss that deadline; it is now 30 seconds.

Both were observed as e2e failures on unrelated PRs (#4427, #4439).

Assisted-by: AI
…erbosity

; Conflicts:
;	docs/pages/release_notes.rst
@reinkrul
reinkrul merged commit 8780280 into master Aug 18, 2026
12 checks passed
@reinkrul
reinkrul deleted the fix/chart-default-verbosity branch August 18, 2026 07:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants