Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Timer in SQL Lab and Explore doesn't work

See original GitHub issue

A clear and concise description of what the bug is. The timer in SQL Lab doesn’t work. When you run the query 1st time, it shows some number (unsure if accurate). When you run a query 2nd time the value on the timer doesn’t change.

Expected results

The timer should reset every time user hits the “RUN” button, and start counting again from 0.

Actual results

Timer is stuck.

Screenshots

Step 1: Running 1st query: (timer has some result, which looks inacurate, the query took longer than 0.67 sec sqllab-timer-bug Timer detail: Screen Shot 2020-09-11 at 5 55 40 PM

Step 2: Change to different SQL Lab tab and run 2nd query: step1 Timer detail: Screen Shot 2020-09-11 at 5 56 02 PM

See query is running - timer value doesn’t change step2 Timer detail: Screen Shot 2020-09-11 at 5 56 08 PM

Query finished and returned result - timer is still displaying same value as before hitting RUN button: steap3 Timer detail: Screen Shot 2020-09-11 at 5 56 13 PM

How to reproduce the bug

Go to SQL Lab
Click on RUN query
See the timer and whether it changes
Run query again, see the timer and whether it changes

Environment

superset version: latest

Checklist

Make sure these boxes are checked before submitting your issue - thank you!

I have checked the superset logs for python stacktraces and included it here as text if there are any.
I have reproduced the issue with at least the latest released version of superset.
I have checked the issue tracker for the same issue and I haven’t found one similar.