Cerberus112 commented on issue #27160: URL: https://github.com/apache/superset/issues/27160#issuecomment-2656068850
I recently discovered something that, if I'm not mistaken, although the automatic warmup process works, it is not useful since the cached chart is not retrieved from the front. First, create a script that acts as a warmup cache, but using the /api/v1/chart/warm_up_cache endpoint, the same one used by the celery task: [https://github.com/apache/superset/blob/master/superset/tasks/cache.py](url) The result of the caches is satisfactory in all cases except for a few non-relevant exceptions: `[2025-02-13 10:30:49] Chart 443 cached. Response: {'result': [{'chart_id': 443, 'viz_error': None, 'viz_status': 'success'}]}` But if I consult the same graph, the cache date does not correspond to the moment of caching launched by endpoint:  Any workaround for this problem? -- 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]
