rusackas opened a new pull request, #42400:
URL: https://github.com/apache/superset/pull/42400

   ### SUMMARY
   When configuration-schema enrichment fails (connection refused, driver 
hiccups, etc.), the raw exception text was passed through to the UI as a danger 
toast. That reads as raw internals, varies wildly by driver, and isn't 
translatable. This swaps it for a stable, translatable message pointing at the 
server logs, where the full exception is already recorded via 
`logger.exception`.
   
   ### BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
   Before: toast shows e.g. `connection failed` (whatever the driver raised).
   After: toast shows "Could not load metadata for this configuration; showing 
the default form. See the server logs for details."
   
   ### TESTING INSTRUCTIONS
   ```bash
   pytest tests/unit_tests/semantic_layers/api_test.py
   ```
   Or point a semantic layer config at an unreachable host in the modal and 
confirm the toast shows the new message while the fallback form still renders.
   
   ### ADDITIONAL INFORMATION
   - [ ] Has associated issue:
   - [ ] Required feature flags:
   - [x] Changes UI
   - [ ] Includes DB Migration (follow approval process in 
[SIP-59](https://github.com/apache/superset/issues/13351))
     - [ ] Migration is atomic, supports rollback & is backwards-compatible
     - [ ] Confirm DB migration upgrade and downgrade tested
     - [ ] Runtime estimates and downtime expectations provided
   - [ ] Introduces new feature or API
   - [ ] Removes existing feature or API
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)


-- 
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]

Reply via email to