Skip to content
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

[explore] improve database error handling #11879

Closed
mistercrunch opened this issue Dec 1, 2020 · 1 comment
Closed

[explore] improve database error handling #11879

mistercrunch opened this issue Dec 1, 2020 · 1 comment
Labels
#bug:cosmetic Cosmetic/layout/design tweak needed global:error Related to global errors affecting the platform

Comments

@mistercrunch
Copy link
Member

mistercrunch commented Dec 1, 2020

Screenshot

Screen Shot 2020-12-01 at 9 40 40 AM

Screen Shot 2020-12-01 at 9 40 34 AM

Description

This kind of error (DatabaseError) should be expected and handled well. It should really say something like BigQuery error and offer the right detail as well as monospace-formatted details.

Somehow SQL Lab does a better job at surfacing the error message from the database:
Screen Shot 2020-12-01 at 9 43 11 AM

We may need database-specific handling of error message strings, so that we can decompose a title, subtitle (one line message) and a longer description. For BigQuery for example, it'd be nice to show only that first string and allow to expand the longer multi-line blob.

@mistercrunch mistercrunch added the #bug:cosmetic Cosmetic/layout/design tweak needed label Dec 1, 2020
@junlincc junlincc added global:error Related to global errors affecting the platform and removed preset-io labels Dec 1, 2020
@nytai
Copy link
Member

nytai commented Apr 21, 2021

This should be fixed by #14040. If I'm incorrect, please reopen

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
#bug:cosmetic Cosmetic/layout/design tweak needed global:error Related to global errors affecting the platform
Projects
None yet
Development

No branches or pull requests

3 participants