bito-code-review[bot] commented on PR #35923:
URL: https://github.com/apache/superset/pull/35923#issuecomment-3471578249

   <details open>
     <summary><strong>Interaction Diagram by <a 
href="https://bito.ai#sequence_diagram";>Bito</a></strong></summary>
   
   ```mermaid
   sequenceDiagram
   participant Scheduler as Celery Beat Scheduler
   participant CacheTask as cache_warmup Task<br/>🔄 Updated | ●●● High
   participant Strategy as Strategy Classes<br/>🔄 Updated | ●●● High
   participant SecMgr as SecurityManager
   participant WebDriver as WebDriverSelenium<br/>🔄 Updated | ●●● High
   participant Dashboard as Dashboard Model
   participant Screenshot as Screenshot Capture
   Scheduler->>CacheTask: Trigger cache-warmup (CELERYBEAT_SCHEDULE)
   CacheTask->>Strategy: Load strategy by name
   Strategy->>Dashboard: Query published dashboards
   Dashboard-->>Strategy: Return dashboard URLs
   CacheTask->>SecMgr: find_user(SUPERSET_CACHE_WARMUP_USER)
   SecMgr-->>CacheTask: Return authenticated user
   CacheTask->>WebDriver: Initialize WebDriverSelenium(user)
   CacheTask->>WebDriver: get_screenshot(url, grid-container)
   WebDriver->>Screenshot: Capture dashboard via WebDriver
   Screenshot-->>WebDriver: Return screenshot bytes
   WebDriver-->>CacheTask: Screenshot result
   CacheTask-->>Scheduler: Return success/error results
   ```
   Critical path: Celery Beat Scheduler -&gt; cache_warmup Task -&gt; Strategy 
Classes -&gt; Dashboard Model -&gt; WebDriverSelenium -&gt; Screenshot Capture
   
   
   > **Note:** Cache warmup refactored from chart-based API calls to 
dashboard-based WebDriver screenshots. User authentication now happens at task 
initialization via SecurityManager. WebDriverSelenium now manages its own 
lifecycle with lazy driver creation and automatic cleanup.
   
   </details>


-- 
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]

Reply via email to