rinimisinii opened a new issue, #37707: URL: https://github.com/apache/superset/issues/37707
## Screenshot <img width="1917" height="1086" alt="Image" src="https://github.com/user-attachments/assets/8332fc17-b3a4-402a-9797-6898ad772966"; /> ## Description When migrating a Superset instance from SQLite to PostgreSQL, very long database error messages can overflow the UI. In the current behavior, long error strings: - Extend beyond the visible container - Are hard to read in full - Make copy & paste difficult, especially when debugging or sharing the error externally This becomes particularly problematic during database migrations, where database errors are often verbose and need to be copied verbatim for troubleshooting. ## Design input No specific design input required at this stage. This is primarily a usability issue. The expectation is simply that long error messages are rendered in a way that remains readable and easy to copy (e.g. wrapping or scrolling), consistent with existing Superset UI patterns. ## Steps to reproduce 1. Migrate an existing Superset metadata database from SQLite to PostgreSQL 2. Start Superset and trigger database initialization or validation 3. Ensure a schema mismatch exists (for example, a foreign key constraint where column types differ, such as string vs uint) -- 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]
