cwegener opened a new issue, #23288: URL: https://github.com/apache/superset/issues/23288
After #23186 , the `superset` Flask cli no longer starts unless a non-default SECRET_KEY is configured. #### How to reproduce the bug 1. Checkout PR #23186 2. Enable Flask Debug: `export FLASK_DEBUG=True` 3. Run `superset --help` 4. See error: `Refusing to start due to insecure SECRET_KEY` ### Expected results `superset` CLI prints out the help page ### Actual results error: `Refusing to start due to insecure SECRET_KEY` ### Environment (please complete the following information): - browser type and version: NA - superset version: PR #23186 - python version: `3.10` - node.js version: NA - any feature flags active: ### Checklist Make sure to follow these steps before submitting your issue - thank you! - [x] 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. - [x] I have checked the issue tracker for the same issue and I haven't found one similar. -- 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]
