Bug description
- Open SQL Lab
- Use two or more tabs
- perform a query -- without switching tabs results are shown
- switch to other tab and run query
Observed:
5. no results shown
Expected: results are shown
Workaround: reload, re-run query
Screenshots/recordings
No response
Superset version
master / latest-dev
Python version
3.9
Node version
16
Browser
Chrome
Additional context
based on official docker image with add. db drivers (duckdb)
Checklist
- [ ] I have searched Superset docs and Slack and didn't find a solution to my problem.
- [ ] I have searched the GitHub issue tracker and didn't find a similar bug report.
- [ ] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.
Comment From: dosubot[bot]
Hi @schwebke! I'm Dosu and I’m helping the superset team.
This issue isn't tracked in existing Superset issues or docs, but recent changes in SQL Lab tab management are likely related. The latest master branch introduced a new immutableId for query editor tabs to improve event routing and tab identification, aiming to fix problems where tab IDs changed after syncing with the backend, causing React to flush and re-render tabs, which could disrupt result rendering after tab switches. These changes are meant to ensure query results and events are correctly associated with the active tab, even after switching or persistence operations [PR #35105] [PR #34720].
If you're running the latest-dev branch, you should be getting these improvements, but there may still be edge cases or regressions. The only known workaround is to reload and re-run the query. If you want to dig deeper, check that the immutableId is correctly propagated in your environment and that Redux state updates for tab switching and query execution are working as expected. Monitoring for further upstream fixes or testing after future merges may help if the issue persists.
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other 
Comment From: msyavuz
I can't reproduce in master, @sadpandajoe any ideas?
Comment From: sadpandajoe
@msyavuz if we can't repro consistently or the steps aren't there, I think we can close this out. Could be that this has already been fixed in master. One other thing you can do is see if you can repro in 6.0.0rc1 if you can then update your local to master and try again and if you can't then close it as it's probably fixed from another PR
Comment From: msyavuz
Closing this one as it seems to be fixed on master
Comment From: schwebke
@msyavuz rechecked with 6rc2 -- no issue there as well