Skip to content
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

Superset loading indefinitely at startup #30831

Closed
3 tasks done
isc-jgupta opened this issue Nov 4, 2024 · 4 comments
Closed
3 tasks done

Superset loading indefinitely at startup #30831

isc-jgupta opened this issue Nov 4, 2024 · 4 comments
Labels
dashboard:native-filters Related to the native filters of the Dashboard dashboard:performance Related to Dashboard performance

Comments

@isc-jgupta
Copy link

Bug description

Currently running on superset on an ubuntu container with apache-superset running on python. I am running version 4.0.2 of superset. I have 3 tabs with 6 graphs each and in one tab (called tab3) there are two filters that are required and use
'Select first filter value by default'. I know that this issue has been resolved before, but it seems like its an issue for the python library. The screenshot below shows it loading on startup and it stays that way unless I change the filter so that it doesnt select the first value by default. I need this option for my project however.

Screenshots/recordings

Screenshot 2024-11-04 at 11 16 12 AM

Superset version

4.0.2

Python version

I don't know

Node version

Not applicable

Browser

Chrome

Additional context

No response

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.
Copy link

dosubot bot commented Nov 4, 2024

The issue you're experiencing with Superset version 4.0.2 loading indefinitely when using the 'Select first filter value by default' option is a known problem. This occurs when filters with this option checked cannot be loaded, preventing the dashboard from rendering. A similar issue was discussed in a closed thread, where it was suggested to uncheck the 'Select first filter value by default' option as a workaround until the bug is patched [1].

The problem is related to the filters not being initialized properly, which causes the dashboard to wait indefinitely for them to load [2]. Unfortunately, if you need this option for your project, you might need to wait for a patch or consider alternative ways to handle the filter initialization.

To continue talking to Dosu, mention @dosu.

@dosubot dosubot bot added dashboard:native-filters Related to the native filters of the Dashboard dashboard:performance Related to Dashboard performance labels Nov 4, 2024
@geido
Copy link
Member

geido commented Nov 4, 2024

Hello @isc-jgupta from your screenshot it seems that all filters are out of scope? I am wondering if this an issue that happens only when every filter is not in scope and 'Select first filter value by default' is enabled for one of those.

@isc-jgupta
Copy link
Author

i think all the filters are out of scope because the tabs havent loaded. If the tabs loaded it should be fewer filters out of scope and the first tab has all the filters with 'Select first filter value by default'

@isc-jgupta
Copy link
Author

okay so it looks like the issue was the table with the 'Select first filter value by default' filter applied to it had no data on startup. when I loaded the table with some data, it loaded fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dashboard:native-filters Related to the native filters of the Dashboard dashboard:performance Related to Dashboard performance
Projects
None yet
Development

No branches or pull requests

2 participants