GitHub user virtualb0x edited a comment on the discussion: Cache warm_up logic?
Well. I've checked one more time: api-user make successful warmups: [2025-08-29 05:04:44,708: INFO/ForkPoolWorker-6] fetch_url[39048dc0-b6f8-40d2-9049-c8618997724d]: Fetched http://superset-debug:8088/api/v1/chart/warm_up_cache with payload {"chart_id": 1382}, status code: 200 | -- | -- | | 2025-08-29 08:04:28.785 | [2025-08-29 05:04:28,785: INFO/ForkPoolWorker-6] fetch_url[39048dc0-b6f8-40d2-9049-c8618997724d]: Fetching http://superset-debug:8088/api/v1/chart/warm_up_cache with payload {"chart_id": 1382} | | | 2025-08-29 08:04:00.263 | [2025-08-29 05:04:00,263: INFO/ForkPoolWorker-31] cache-warmup[6ee13036-d619-4b35-b403-b8f17a8a6d51]: Scheduling {"chart_id": 1382} but when I login to superset UI via this user, the queries are started again trying to fetch data from sources via trino Still can't understand why do this happens if the user is the same. How Can I avoid it GitHub link: https://github.com/apache/superset/discussions/34837#discussioncomment-14253126 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
