Uh oh!
There was an error while loading. Please reload this page.
fix(bulk-operations): surface errors on console when console logs are off [DX-10224] - #352
Conversation
… off Bulk command failures were silently swallowed when log.showConsoleLogs was disabled — handleAndLogError only reaches the console through the winston error transport, which is silenced in that mode, so the terminal showed nothing on failure (e.g. an invalid stack API key). Print a user-facing error line in BaseBulkCommand.catch() when console logs are off, reusing cliErrorHandler.classifyError so the message matches the friendly text written to the log file. Guarded to avoid double-printing when console logs are on. Ref: DX-10224 Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
🔒 Security Scan Results
⏱️ SLA Breach Summary
✅ BUILD PASSED - All security checks passed |
🔒 Security Scan Results
⏱️ SLA Breach Summary
✅ BUILD PASSED - All security checks passed |
…into fix/DX-10224-bulk-error-visibility
🔒 Security Scan Results
⏱️ SLA Breach Summary
✅ BUILD PASSED - All security checks passed |
…lity
Post-merge, the console-log state moved from configHandler.get('log').
showConsoleLogs to the process-wide console-policy module, and the
configHandler import was dropped. catch() still referenced configHandler,
breaking the build (TS2304).
Switch the guard to isConsoleLogEnabled() so the friendly error line still
prints on failure when console logs are off, without double-printing when
they are on. Matches the convention the rest of the file now follows.
Ref: DX-10224
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>🔒 Security Scan Results
⏱️ SLA Breach Summary
✅ BUILD PASSED - All security checks passed |
harshitha-cstk
commented
Aug 19, 2026
opened a new PR: #355 |
🔒 Security Scan Results
⏱️ SLA Breach Summary
✅ BUILD PASSED - All security checks passed |
Summary
Bulk command failures (
cm:stacks:bulk-entries/bulk-assets/bulk-taxonomies) were silently swallowed whenlog.showConsoleLogswas disabled. The terminal showed nothing on failure — e.g. an invalid stack API key produced zero output — while the same failure printed correctly with console logs on.Root cause
Errors flow through
handleAndLogError→ the winstonerrorlogger, whose console transport is silenced when console logging is off. The only re-emit path inlogErroris guarded byconsoleLevel !== 'error', which is false for normal errors, so nothing reaches the terminal.Fix
Scoped to the bulk-operations plugin (
base-bulk-command.ts) — no changes tocli-utilities. InBaseBulkCommand.catch(), when console logs are off, print a user-facing error line viacliux.print, reusingcliErrorHandler.classifyErrorso the console message matches the friendly text written to the log file. Guarded to avoid double-printing when console logs are on.All three bulk commands inherit this handler, so all are covered.
Verification
🤖 Generated with Claude Code