-
Notifications
You must be signed in to change notification settings - Fork 14.6k
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
SQL Lab: Stop query button sometimes results in "Internal Server Error" response rendered in results' pane #4926
Comments
fixes apache#4926 In rare cases where the query is stopped before it is started, SQL Lab returns an unexpected string payload instead of a normal dictionary. This aligns the process to handle the error in a homogeneous fashion.
Thanks for reporting this bug. Here's the fix: #4928 |
@mistercrunch that was really fast!
however, i'm pretty sure in my case the query has been started (is "RUNNING" and then gets marked as "USER CANCELED" in Presto). |
fixes #4926 In rare cases where the query is stopped before it is started, SQL Lab returns an unexpected string payload instead of a normal dictionary. This aligns the process to handle the error in a homogeneous fashion.
@mistercrunch, thanks for issuing a release |
I managed to upgrade to Now, when I stop a query after ~6s of its execution I
|
fixes apache#4926 In rare cases where the query is stopped before it is started, SQL Lab returns an unexpected string payload instead of a normal dictionary. This aligns the process to handle the error in a homogeneous fashion.
fixes apache#4926 In rare cases where the query is stopped before it is started, SQL Lab returns an unexpected string payload instead of a normal dictionary. This aligns the process to handle the error in a homogeneous fashion.
fixes apache#4926 In rare cases where the query is stopped before it is started, SQL Lab returns an unexpected string payload instead of a normal dictionary. This aligns the process to handle the error in a homogeneous fashion.
Make sure these boxes are checked before submitting your issue - thank you!
Superset version
0.24.0
Expected results
Query stopped.
Actual results
UI:
Yellow rectangle with "Query was stopped" is shown for a moment, but then it's replaced with a red rectangle with the following:
screenshot:

Webapp output:
Steps to reproduce
My superset configuration:
Web app is run with:
The text was updated successfully, but these errors were encountered: