Unable to go anywhere from loading page. I am adding a scrrenshot

anjali-systango commented 2 weeks ago

Bug description

it says unable to locate loader.png and it never goes beyond that after singing in with admin id and pass asz admin

Screenshots/recordings

superset issue

Superset version

master / latest-dev

Python version

3.9

Node version

16

Browser

Firefox

Additional context

No response

Checklist

[x] I have searched Superset docs and Slack and didn't find a solution to my problem.
[x] I have searched the GitHub issue tracker and didn't find a similar bug report.
[x] 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.

dosubot[bot] commented 2 weeks ago

Hey @anjali-systango! 👋 I'm here to help you with any bugs, questions, or contributions you have for the project. Let's tackle this issue together while we wait for a human maintainer to join in.

I couldn't find a specific answer to the 'unable to locate loader.png' error in the repository. However, there are some general insights on how Apache Superset handles static resource loading that might help you troubleshoot this issue.

Superset's frontend uses a component called ImageLoader to handle the loading of images and other static assets. This component attempts to fetch images from a specified source URL and uses a fallback image if the fetch fails. If the image is not found, it logs an error and defaults to the fallback image ^[1].

To address this issue, you might want to check the following:

Static Asset Paths: Ensure that the paths to your static assets are correctly configured. The default paths for static assets in Superset are specified in the configuration file, such as VERSION_INFO_FILE and PACKAGE_JSON_FILE ^[2].
Browser Console: Check the browser console for any errors related to loading static resources. This might provide more specific information about why the loader.png is not being found.
Superset Logs: Configure Superset logs to provide more detailed information by setting the LOG_LEVEL to DEBUG in your configuration file. This can help capture detailed logs about resource loading errors ^[2].

If these steps do not resolve the issue, it might be helpful to look into any recent changes in the latest-dev version of Superset that could affect static resource loading, although I couldn't find specific known issues related to this ^[2].

To continue talking to Dosu, mention @dosu.

rusackas commented 2 weeks ago

Looks like the frontend isn't built... how did you install/run Superset? Docker, or another means? Are you running webpack in a separate thread? In dev mode?

apache / superset