Dashboard shows endless loading

[jacobcroope]

Upon initially loading a dashboard filters load and populate while the dashboard spins it's logo endlessly. A manual refresh causes a normal loading behavior.

How to reproduce the bug

See screenshot.

1. Go to any dashboard
2. Wait for it to load
3. Hit refresh on your browser to get it to load correctly after waiting.

Expected results

Dashboard fully loads.

Actual results

Dashboard only loads after refresh.

Screenshots

Loading.Error.mp4

Environment

• Windows 10,11 and Firefox, Chrome, Safari, and Edge.

• Superset Version 1.3, 1.5, 2.0

• docker-compose install currently version 2.0 but tried on all of the recent versions.

• python 3.8.10

• [x ] 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.

This has been an annoying issue that prevents us from rolling this out to customers.

[jacobcroope]

There seems to be something related to filters out of scope as that can trigger the dashboard to load.

Superset.-.Work.-.Microsoft_.Edge.2022-07-18.09-58-22_Trim.mp4

[jacobcroope]

Someone suggested that "Select first filter item" seems to be the culprit and removing it does seem to fix the problem. However, that feature is needed for us to use Row Level Security and Roles and not have to create a unique Dashboard for every user/organization combo so more of a temporary work around if you don't need that feature.

[japitts0889]

Not sure if this is the right issue or not to mention this as I see there's multiple linked for it or if it warrants opening up a new issue?

I had this issue on 2.1.0 and recently updated to 2.1.1 after seeing this thread and that the change got merged into that version, but after updating i'm still getting the spinning dashboards when having the "Select first filter value by default" filter configuration selected.

[smace-biaux]

Hello

Do you know if this issue will be corrected in v1 ?
We do not have the means to upgrade to v2.

Thank you very much.

Cordially

[unnyns-307]

Also encounter this issue in V.2.1.1. Is this fixed on V.3.0.0?
@eschutho if not so, could we reopen this issue?

[sundaram-dubey]

Is this issue fixed yet? Or anyone has found any workaround?

[Slaheddine]

I am having the same issue, with no solution found, is there any fix please ? (#28833)

[sfirke]

Hi all - this issue was due to a bug related to filters out of scope, the fix has been merged into master branch for well over a year and is present in all versions >3.0.0. Please file new behaviors like this as new bugs -- thank you @Slaheddine for doing so. Just posting this so people know this issue is closed and pertains to a specific bug from version ~2.0.0.