worker24h opened a new issue, #31862:
URL: https://github.com/apache/superset/issues/31862
### Bug description
1. I used MYSQL to store metadata.
2. The first stage `Applying DB migrations` is hanging
```python
Skipping local overrides
Unknown Operation!!!
######################################################################
Init Step 1/4 [Starting] -- Applying DB migrations
######################################################################
--------------------------------------------------------------------------------
WARNING
--------------------------------------------------------------------------------
A Default SECRET_KEY was detected, please use superset_config.py to override
it.
Use a strong complex alphanumeric string and use a tool to help you generate
a sufficiently random sequence, ex: openssl rand -base64 42
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Refusing to start due to insecure SECRET_KEY
Environment set to: dev
[2025-01-15 16:24:11 +0800] [36] [INFO] Starting gunicorn 22.0.0
[2025-01-15 16:24:11 +0800] [36] [INFO] Listening at: http://0.0.0.0:8088
(36)
[2025-01-15 16:24:11 +0800] [36] [INFO] Using worker: gthread
[2025-01-15 16:24:11 +0800] [37] [INFO] Booting worker with pid: 37
2025-01-15 16:24:12,904:DEBUG:superset.utils.logging_configurator:logging
was configured successfully
2025-01-15 16:24:12,910:DEBUG:root:Configured event logger of type <class
'superset.utils.log.DBEventLogger'>
2025-01-15 16:24:12,911:WARNING:superset.initialization:We haven't found any
Content Security Policy (CSP) defined in the configurations. Please make sure
to configure CSP using the TALISMAN_ENABLED and TALISMAN_CONFIG keys or any
other external software. Failing to configure CSP have serious security
implications. Check https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP for
more information. You can disable this warning using the
CONTENT_SECURITY_POLICY_WARNING key.
2025-01-15 16:24:12,913:INFO:superset.initialization:Setting database
isolation level to READ COMMITTED
/usr/local/lib/python3.10/site-packages/flask_limiter/extension.py:333:
UserWarning: Using the in-memory storage for tracking rate limits as no storage
was explicitly specified. This is not recommended for production use. See:
https://flask-limiter.readthedocs.io#configuring-a-storage-backend for
documentation about configuring the storage backend.
warnings.warn(
2025-01-15 16:24:13,495:INFO:superset.utils.screenshots:No PIL installation
found
2025-01-15 16:24:13,931:INFO:superset.utils.pdf:No PIL installation found
```
### Screenshots/recordings
_No response_
### Superset version
4.1.1
### Python version
3.10
### Node version
18 or greater
### Browser
Chrome
### 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.
--
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]
