"Could not load default spinner" error pollutes Superset 6.1.0 logs

[sfirke]

Bug description

I deployed Superset 6.1.0. I don't have a custom spinner or custom logo enabled on my instance. I see this repeating in the logs:

2026-05-28 03:32:36,607:WARNING:superset.views.base:Could not load default spinner SVG: [Errno 2] No such file or directory: '/app/superset/views/../../superset-frontend/packages/superset-ui-core/src/components/assets/images/loading.svg'

I don't see anything broken related to how spinners appear in the UI, at first glance.

Screenshots/recordings

No response

Superset version

master / latest-dev

Python version

I don't know

Node version

I don't know

Browser

Firefox

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.

[durgaprasadml]

I investigated this issue and it looks like the backend attempts to load the default spinner SVG from a frontend source path that may not exist in packaged/runtime environments.

The UI appears to fall back correctly, but the missing optional asset causes repeated warning logs.

I’m working on a fix to avoid warning spam when the default spinner asset is unavailable.

[sfirke]

Please no other PRs now that this has been assigned.