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

Uncaught runtime errors when opening the dashboard CSS editor #27137

Closed
3 tasks done
goto-loop opened this issue Feb 16, 2024 · 0 comments · Fixed by #27191
Closed
3 tasks done

Uncaught runtime errors when opening the dashboard CSS editor #27137

goto-loop opened this issue Feb 16, 2024 · 0 comments · Fixed by #27191
Assignees

Comments

@goto-loop
Copy link
Contributor

Bug description

In Superset version 3.1.0, when I want to edit the CSS of a dashboard, the following error message appears. After dismissing it, the CSS editor works as expected.

Uncaught runtime errors:
ERROR
NetworkError: WorkerGlobalScope.importScripts: Failed to load worker script at http://localhost:9099/superset/dashboard/11/worker-css.js (nsresult = 0x80530013)
handleError@webpack-internal:///./node_modules/webpack-dev-server/client/overlay.js:251:58
createOverlay/<@webpack-internal:///./node_modules/webpack-dev-server/client/overlay.js:270:18

How to reproduce the bug

  1. Create a new dashboard
  2. Open the menu on the top right and click "Edit CSS"

Screenshots/recordings

No response

Superset version

3.1.0

Python version

3.11

Node version

16

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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants