-
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
SQL Lab result set panel and timer disappears #26276
Comments
Hi @gaurav7261. Could you complete the template and add a description, screenshots/recording, expected, actual. The problem of linking Slack messages is that they might be deleted or forwarded to a different channel. Having the issue template complete also helps for historical purposes as people might come back to this issue later and understand what happened. |
We also provide a test environment for 3.1.0 RC2 here. Are you able to reproduce your issue there? If not, maybe it would be good to check you browser console and see if there are any errors with your deployment. |
not able to find a query that run for more than 10 sec in test env |
template done |
Did you forget to save? I'm still seeing the old template. |
yes, thanks |
@justinpark could you check if you can reproduce this error? |
I'm not sure if this might be related to this issue but I noticed you are using Node 10 but Superset requires Node 16 to run correctly. |
@gaurav7261 We were able to reproduce your problem in our internal environment. @justinpark will take a look at the issue. |
I have deployed 3.1.0 RC2, but facing weird issue in sqllab, timer is out of display after 10 sec, but when i refresh, it comes again, tried in chrome, safari, also nothing in logs to debug.
How to reproduce the bug
Expected results
timer should be there until query run/failed
Actual results
timer gone after 10 sec
Screenshots
Screen.Recording.2023-12-14.at.12.01.47.PM.mov
Environment
3.1.0-RC2
python --version 3.9
v10.19.0
Checklist
Make sure to follow these steps before submitting your issue - thank you!
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: