dosubot[bot] commented on issue #37707: URL: https://github.com/apache/superset/issues/37707#issuecomment-3854760953
<!-- Greeting --> Hi @rinimisinii! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the superset team. <!-- Answer --> Superset’s error message UI is inconsistent across different parts of the app. In SQL Lab, long database errors are shown in a scrollable, pre-wrapped monospace block with a copy-to-clipboard button, making them easy to read and copy. However, in chart, dashboard, and migration contexts, errors are rendered using components like `DatabaseErrorMessage` and `ErrorAlert`, which rely on static alert banners. These banners use pre-wrap styling for readability, but they don’t always provide scrollbars or copy helpers, so long messages can still overflow and be hard to copy or fully view [[ErrorAlert code](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset-frontend/src/components/ErrorMessage/ErrorAlert.tsx#L30-L137)][[DatabaseErrorMessage code](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset-frontend/src/components/ErrorMessage/DatabaseErrorMessage.tsx#L26-L90)]. Superset’s design guidelines recommend using expandable banners and modals for long error messages, but not all UI areas implement these patterns consistently. There’s no configuration or feature flag to restore the more robust error display from older versions; code changes are needed to add scrollable containers or copy buttons in chart/dashboard error banners [[Design Guidelines](https://github.com/apache/superset/wiki/Error-Message-Design-Guidelines)]. As a workaround, you can use your browser’s developer tools to inspect and copy the full error message if it overflows the UI. For a more permanent fix, consider updating the relevant error display components to use scrollable containers and add a copy-to-clipboard button, similar to what’s done in SQL Lab. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/e71c4fc6-0ca8-4f8f-aa99-55e00859560f?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/e71c4fc6-0ca8-4f8f-aa99-55e00859560f?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/e71c4fc6-0ca8-4f8f-aa99-55e00859560f?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/e71c4fc6-0ca8-4f8f-aa99-55e00859560f?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/e71c4fc6-0ca8-4f8f-aa99-55e00859560f?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/e71c4fc6-0ca8-4f8f-aa99-55e00859560f?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/e71c4fc6-0ca8-4f8f-aa99-55e00859560f?feedback_type=other)</sup> [](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github) [](https://cursor.com/link/prompt?text=Superset%E2%80%99s%20error%20message%20UI%20is%20inconsistent%20across%20different%20parts%20of%20the%20app.%20In%20SQL%20Lab%2C%20long%20database%20errors%20are%20shown%20in%20a%20scrollable%2C%20pre-wrapped%20monospace%20block%20with%20a%20copy-to-clipboard%20button%2C%20making%20them%20easy%20to%20read%20and%20copy.%20However%2C%20in%20chart%2C%20dashboard%2C%20and%20migration%20contexts%2C%20errors%20are%20rendered%20using%20components%20like%20%60DatabaseErrorMessage%60%20and%20%60ErrorAlert%60%2C%20which%20rely%20on%20static%20alert%20banners.%20These%20banners%20use%20pre-wrap%20styling%20for%20readability%2C%20but%20they%20don%E2%80%99t%20always%20provide%20scrollbars%20or%20copy%20helpers%2C%20so%20long%20messages%20can%20still%20overflow% 20and%20be%20hard%20to%20copy%20or%20fully%20view%20%5B%5BErrorAlert%20code%5D%28https%3A//github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset-frontend/src/components/ErrorMessage/ErrorAlert.tsx%23L30-L137%29%5D%5B%5BDatabaseErrorMessage%20code%5D%28https%3A//github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset-frontend/src/components/ErrorMessage/DatabaseErrorMessage.tsx%23L26-L90%29%5D.%0A%0ASuperset%E2%80%99s%20design%20guidelines%20recommend%20using%20expandable%20banners%20and%20modals%20for%20long%20error%20messages%2C%20but%20not%20all%20UI%20areas%20implement%20these%20patterns%20consistently.%20There%E2%80%99s%20no%20configuration%20or%20feature%20flag%20to%20restore%20the%20more%20robust%20error%20display%20from%20older%20versions%3B%20code%20changes%20are%20needed%20to%20add%20scrollable%20containers%20or%20copy%20buttons%20in%20chart/dashboard%20error%20banners%20%5B%5BDesign%20Guidelines%5D%28https%3A//github.co m/apache/superset/wiki/Error-Message-Design-Guidelines%29%5D.%0A%0AAs%20a%20workaround%2C%20you%20can%20use%20your%20browser%E2%80%99s%20developer%20tools%20to%20inspect%20and%20copy%20the%20full%20error%20message%20if%20it%20overflows%20the%20UI.%20For%20a%20more%20permanent%20fix%2C%20consider%20updating%20the%20relevant%20error%20display%20components%20to%20use%20scrollable%20containers%20and%20add%20a%20copy-to-clipboard%20button%2C%20similar%20to%20what%E2%80%99s%20done%20in%20SQL%20Lab.) [](https://go.dosu.dev/discord-bot) [](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/issues/37707) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
