Skip to content

fix(cli): report invalid log levels for maintenance runs - #5586

Merged
julio-lopez merged 4 commits into
kopia:masterfrom
justadityaraj:fix/invalid-log-level-error
Sep 9, 2026
Merged

julio-lopez merged 4 commits into
kopia:masterfrom
justadityaraj:fix/invalid-log-level-error

Conversation

@justadityaraj

@justadityaraj justadityaraj commented Aug 27, 2026 •

Copy link
Copy Markdown
Contributor

Context

maintenance run --safety=none could replace an invalid global flag error with the unrelated unhandled safety level message because the safety flag's backing value remained empty until Kingpin applied its default.

Changes

Initialize the backing value to the safety flag's documented default before parser hooks run, and cover the invalid log-level path with a regression test.

User impact

Invalid log levels used with maintenance runs now report the allowed values so the flag can be corrected directly.

Verification

  • go test ./cli -run '^TestMaintenanceRunReportsInvalidGlobalFlag$' -count=1 -v
  • go test ./cli -count=1
  • go vet -all ./cli
  • golangci-lint run ./cli/...
  • gopls check cli/app.go cli/command_maintenance_run_test.go

@justadityaraj
justadityaraj requested a review from a team August 27, 2026 06:15
Comment thread cli/command_maintenance_run_test.go Resolved
@codecov

codecov Bot commented Sep 9, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 77.80%. Comparing base (cb455c6) to head (0578329).
⚠️ Report is 1086 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #5586      +/-   ##
==========================================
+ Coverage   75.86%   77.80%   +1.93%     
==========================================
  Files         470      553      +83     
  Lines       37301    31806    -5495     
==========================================
- Hits        28299    24746    -3553     
+ Misses       7071     4982    -2089     
- Partials     1931     2078     +147     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Comment thread cli/command_maintenance_run_test.go Resolved
@julio-lopez
julio-lopez merged commit 2602713 into kopia:master Sep 9, 2026
28 checks passed
@julio-lopez

Copy link
Copy Markdown
Collaborator

Thanks @justadityaraj

julio-lopez added a commit to julio-lopez/kopia that referenced this pull request Sep 18, 2026
* kopia/master:
  refactor(testing): check for `Scan()` errors in CLITest env (kopia#5626)
  refactor(testing): server control tests (kopia#5642)
  build(deps): bump the common-golang-dependencies group with 10 updates (kopia#5644)
  fix(testing): TestServerControlSocketActivated flake (kopia#5643)
  refactor(server): remove `tls.Config.VerifyPeerCertificate` (kopia#5637)
  fix(providers): wait for ssh process to exit to avoid leaving zombie processes (kopia#5558)
  fix(cli): mark `snapshot verify --parallel` as deprecated and no-op (kopia#5552)
  fix(testing): avoid clobbering storage used for t.Cleanup (kopia#5636)
  fix(testing): prevent panic in Azure versioned storage test (kopia#5635)
  build(infra): avoid persisting credentials in actions/checkout (kopia#5633)
  fix(cli): reject negative values for --parallel flags (kopia#5484)
  fix(cli): report invalid log levels for maintenance runs (kopia#5586)
  feat(ui): upgraded htmlui to the latest version (kopia#5630)
  build(deps-dev): bump electron (kopia#5631)
  build(deps): bump nanoid from 3.3.16 to 3.3.18 in /site in the npm_and_yarn group across 1 directory (kopia#5629)
  refactor(general): propagate `TLSConfigTrustingSingleCertificate` error (kopia#5628)
  refactor(testing): use `ContextForCleanup()` in `t.Cleanup()` (kopia#5627)
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.

Incorrect log-level flag use shows incorrect error on safety flag

2 participants