From bc82e824b02a831afe77c6d1d7be9c109b86529c Mon Sep 17 00:00:00 2001
From: nuyb <103496262+wlswo@users.noreply.github.com>
Date: Thu, 21 May 2026 00:01:09 +0900
Subject: [PATCH] fix: log uncaught explore module errors with console.error
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

`ErrorBoundary.componentDidCatch` in the explore view logs the uncaught
render error through `console.log`:

    componentDidCatch(error: Error, errorInfo: React.ErrorInfo) {
      console.log('Module content error:', error, errorInfo);
    }

`componentDidCatch` is React's canonical error-reporting hook — by the
time it runs, an exception has already propagated up the render tree
and the subtree has been swapped out for the fallback UI. Logging it at
`log` severity hides the failure from the browser DevTools "Errors"
filter and from any tooling (test harnesses, CI log scrapers, error
reporters) that watches `console.error`.

Switch to `console.error` so uncaught errors in explore modules are
surfaced at the appropriate severity. No other behavior change.
---
 .../explore-view/components/error-boundary/error-boundary.tsx   | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/web-console/src/views/explore-view/components/error-boundary/error-boundary.tsx b/web-console/src/views/explore-view/components/error-boundary/error-boundary.tsx
index 21172c1bd715..f0dc879cedfb 100644
--- a/web-console/src/views/explore-view/components/error-boundary/error-boundary.tsx
+++ b/web-console/src/views/explore-view/components/error-boundary/error-boundary.tsx
@@ -38,7 +38,7 @@ export class ErrorBoundary extends React.Component<
   }
 
   componentDidCatch(error: Error, errorInfo: React.ErrorInfo) {
-    console.log('Module content error:', error, errorInfo);
+    console.error('Module content error:', error, errorInfo);
   }
 
   render() {