dosubot[bot] commented on issue #30402: URL: https://github.com/apache/superset/issues/30402#issuecomment-2810914991
<!-- Answer --> Given the information provided, here are some additional suggestions to address the issue of Superset dashboards getting stuck on the loader when embedded in an Angular application: 1. **Asset Loading Optimization**: Since loading multiple dashboards simultaneously causes a slowdown, consider optimizing asset loading. Ensure that common assets (JS, CSS) are cached effectively to prevent redundant downloads. You might also explore lazy loading techniques for assets specific to each dashboard. 2. **Network and Browser Caching**: Verify that your server and browser caching settings are optimized. Proper caching can significantly reduce load times by reusing previously loaded resources. 3. **Concurrency Management**: Limit the number of concurrent requests to the server when loading multiple dashboards. This can prevent server overload and improve response times. 4. **Error Handling in Safari**: The HTTP 400 error in Safari suggests a potential issue with request parameters or headers. Double-check the requests being made in Safari to ensure they match those in other browsers. Consider adding more robust error handling and logging to capture detailed information about these failures. 5. **Angular Change Detection**: Ensure that Angular's change detection isn't causing unnecessary re-renders or updates. You might need to adjust the change detection strategy or use `OnPush` to minimize unnecessary checks. 6. **Superset Configuration**: Review Superset's configuration settings related to embedding and performance. Ensure that settings like `SUPERSET_FEATURE_EMBEDDED_SUPERSET` and others related to embedding are correctly configured. 7. **Debugging and Logging**: Implement detailed logging both in your Angular application and Superset to capture more information about when and why the issue occurs. This can help identify patterns or specific conditions that trigger the problem. If these suggestions do not resolve the issue, it might be beneficial to isolate the problem by testing with a minimal setup (e.g., fewer dashboards, simpler configurations) to identify the root cause. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/4b8ee817-71fd-443e-b5c5-220d687b2237?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/4b8ee817-71fd-443e-b5c5-220d687b2237?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/4b8ee817-71fd-443e-b5c5-220d687b2237?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/4b8ee817-71fd-443e-b5c5-220d687b2237?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/4b8ee817-71fd-443e-b5c5-220d687b2237?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/4b8ee817-71fd-443e-b5c5-220d687b2237?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/4b8ee817-71fd-443e-b5c5-220d687b2237?feedback_type=other)</sup> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
