-
Notifications
You must be signed in to change notification settings - Fork 16.5k
Closed
Labels
inactiveInactive for >= 30 daysInactive for >= 30 days
Description
Application hangs after login with admin account.
Expected results
The application is up and running
Actual results
The application stuck right after login:
How to reproduce the bug
- git clone
- docker-compose up
- open http://localhost:8088/
- login with admin/admin
Environment
(please complete the following information):
- superset version: current master 540df26
- python version:
python --version - node.js version:
node -v - npm version:
npm -v
Checklist
Make sure these boxes are checked before submitting your issue - thank you!
- I have checked the superset logs for python stacktraces and included it here as text if there are any.
- I have reproduced the issue with at least the latest released version of superset.
- I have checked the issue tracker for the same issue and I haven't found one similar.
Additional context
superset-node_1 | audited 906857 packages in 74.627s
superset-node_1 |
superset-node_1 | 1 package is looking for funding
superset-node_1 | run `npm fund` for details
superset-node_1 |
superset-node_1 | found 2 moderate severity vulnerabilities
superset-node_1 | run `npm audit fix` to fix them, or `npm audit` for details
superset-node_1 |
superset-node_1 | > [email protected] dev /app/superset/assets
superset-node_1 | > webpack --mode=development --colors --progress --debug --watch
superset-node_1 |
superset-node_1 | sh: 1: webpack: not found
superset-node_1 | npm ERR! code ELIFECYCLE
superset-node_1 | npm ERR! syscall spawn
superset-node_1 | npm ERR! file sh
superset-node_1 | npm ERR! errno ENOENT
superset-node_1 | npm ERR! [email protected] dev: `webpack --mode=development --colors --progress --debug --watch`
superset-node_1 | npm ERR! spawn ENOENT
superset-node_1 | npm ERR!
superset-node_1 | npm ERR! Failed at the [email protected] dev script.
superset-node_1 | npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
Metadata
Metadata
Assignees
Labels
inactiveInactive for >= 30 daysInactive for >= 30 days
