Skip to content

fix(bulk-operations): display taxonomy error messages in progress-manager mode - #319

Closed
harshitha-cstk wants to merge 1 commit into
v2-devfrom
fix/dx-9992
Closed

fix(bulk-operations): display taxonomy error messages in progress-manager mode#319
harshitha-cstk wants to merge 1 commit into
v2-devfrom
fix/dx-9992

Conversation

@harshitha-cstk

Copy link
Copy Markdown
Contributor

Summary

In progress-manager mode (log.showConsoleLogs=false), the cli-utilities logger suppresses errors on the console. As a result, cm:stacks:bulk-taxonomies failures — including setup errors thrown in init()/setupStack() such as "We can't find that Stack" — left the user with a blank screen.

Why taxonomies specifically

bulk-assets/bulk-entries always reach recordModuleSummary(), and the CLIProgressManager summary prints independently of the logger's console suppression — so those commands always show feedback. bulk-taxonomies skips the summary on error (the error bubbles past it) and the error itself is swallowed by the suppressed logger → nothing on screen.

Change

Scoped to bulk-taxonomies.ts:

  • Added a surfaceError() helper that prints the error via cliux only when console logging is suppressed (no-op otherwise, since the logger already prints it), and skips DisplayedError (validators print those directly).
  • Wired it into run()'s catch (operation-phase errors) and a new catch() override (init-phase errors that never reach run()).

Notes

  • No behavior change when showConsoleLogs=true.
  • No dependency changes.

🤖 Generated with Claude Code

…ager mode

In progress-manager mode (log.showConsoleLogs=false) the logger suppresses
errors on the console, so bulk-taxonomies failures — including setup errors
thrown in init() like "We can't find that Stack" — left a blank screen.

Add a surfaceError helper wired into run()'s catch (operation-phase errors)
and a catch() override (init-phase errors that never reach run()). It prints
the message via cliux only when console logging is suppressed, and skips
DisplayedError to avoid duplicating messages validators already print.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@harshitha-cstk
harshitha-cstk requested a review from a team as a code owner July 27, 2026 12:02
@github-actions

Copy link
Copy Markdown

🔒 Security Scan Results

ℹ️ Note: Only vulnerabilities with available fixes (upgrades or patches) are counted toward thresholds.

Check Type Count (with fixes) Without fixes Threshold Result
🔴 Critical Severity 0 0 10 ✅ Passed
🟠 High Severity 18 200 25 ✅ Passed
🟡 Medium Severity 2 2 500 ✅ Passed
🔵 Low Severity 0 0 1000 ✅ Passed

⏱️ SLA Breach Summary

⚠️ Warning: The following vulnerabilities have exceeded their SLA thresholds (days since publication).

Severity Breaches (with fixes) Breaches (no fixes) SLA Threshold (with/no fixes) Status
🔴 Critical 0 0 15 / 30 days ✅ Passed
🟠 High 0 0 30 / 120 days ✅ Passed
🟡 Medium 0 1 90 / 365 days ⚠️ Warning
🔵 Low 0 0 180 / 365 days ✅ Passed

ℹ️ Vulnerabilities Without Available Fixes (Informational Only)

The following vulnerabilities were detected but do not have fixes available (no upgrade or patch). These are excluded from failure thresholds:

  • Critical without fixes: 0
  • High without fixes: 200
  • Medium without fixes: 2
  • Low without fixes: 0

⚠️ BUILD PASSED WITH WARNINGS - SLA breaches detected for issues without available fixes

Consider reviewing these vulnerabilities when fixes become available.

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.

1 participant