-
Notifications
You must be signed in to change notification settings - Fork 14.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: better handle datasource exceptions #13578
Conversation
Codecov Report
@@ Coverage Diff @@
## master #13578 +/- ##
==========================================
- Coverage 77.53% 71.06% -6.48%
==========================================
Files 904 828 -76
Lines 45986 41460 -4526
Branches 5552 4307 -1245
==========================================
- Hits 35657 29462 -6195
- Misses 10195 11998 +1803
+ Partials 134 0 -134
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Small comment
* fix: handle datasource injected security exception * add tests * fix error text on create update dbs * fix lint * revert create update message * fix test * add sqlalchemy exceptions (cherry picked from commit 1e88408)
* fix: handle datasource injected security exception * add tests * fix error text on create update dbs * fix lint * revert create update message * fix test * add sqlalchemy exceptions (cherry picked from commit 1e88408)
* fix: handle datasource injected security exception * add tests * fix error text on create update dbs * fix lint * revert create update message * fix test * add sqlalchemy exceptions
SUMMARY
Fixes
explore
anddashboard
superset API endpoints so that they can more gracefully handle exceptions from the engines. A more special case is by using theDB_CONNECTION_MUTATOR
and raising from there.Previously these endpoint would crash with HTTP 500
ADDITIONAL INFORMATION