Sdreamery opened a new issue, #30003: URL: https://github.com/apache/superset/issues/30003
### Bug description In version 4.0, I have already set the cache storage path and placed it in Redis, where I can see the cached data. However, when starting with gunicorn, I still encounter an exception: 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.    ### How to reproduce the bug I don't know what to do. ### Screenshots/recordings _No response_ ### Superset version master / latest-dev ### Python version 3.9 ### Node version 16 ### Browser Chrome ### Additional context _No response_ ### Checklist - [X] I have searched Superset docs and Slack and didn't find a solution to my problem. - [X] I have searched the GitHub issue tracker and didn't find a similar bug report. - [X] 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]
