kachely opened a new issue #18933: URL: https://github.com/apache/superset/issues/18933
A clear and concise description of what the bug is. #### How to reproduce the bug 1. Start celery 2. Start beat 3. Start flask 4. There is a request from cache_warmup, but data is not be cached. ### Expected results request will be send by this order: /explore/xxx -> /explore_json/xxx or /api/v1/data/xxx ### Actual results request will be sent by this order: /explore/xxx -> break. #### Screenshots I actually setup a cookie in the request to login in with a warmup user. If I do not add this cookie, it will be redirect to login page.  here is the code I used in warm_up ### Environment (please complete the following information): - browser type and version: - superset version: `superset version` - python version: `python --version` - node.js version: `node -v` - any feature flags active: ### Checklist Make sure to follow these steps before submitting your issue - thank you! - [Y ] 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. - [Y ] I have checked the issue tracker for the same issue and I haven't found one similar. ### Additional context Add any other context about the problem here. -- 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]
