gideonn opened a new issue #17809:
URL: https://github.com/apache/superset/issues/17809


   A clear and concise description of what the bug is.
   
   The documentation makes the worker always fetch the latest chrome but a 
hardcoded version is used for the chromedriver. Many a times this mismatches 
and alerts/reports screenshot stop working since the versions are not 
compatible.
   
   Superset worker should always fetch the latest version for chromedriver, 
like it does for the browser
   
   #### How to reproduce the bug
   
   1. Do a new installation of superset on k8s with alerts and reports 
configured
   2. Setup a dashboard/chart
   3. Setup alerts with screenshot against that dashboard/chart
   4. Will get blank email, on checking the logs, it'll say the screenshot 
didn't work because of the browser and chrome driver being incompatible.
   
   ### Expected results
   Screenshot of the chart/dashboard in the email
   
   ### Actual results
   No screenshot in the email
   
   #### Screenshots
   N/A
   
   ### Environment
   
   Below fields are not applicable. This is relevant for all kubernetes 
deployments that have alerts and reports configured.
   (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!
   
   - [x] I have checked the superset logs for python stacktraces and included 
it here as text if there are any.
   - [x] I have reproduced the issue with at least the latest released version 
of superset.
   - [x] I have checked the issue tracker for the same issue and I haven't 
found one similar.
   
   ### Additional context
   
   I've fixed this by fetching the latest version for chromedriver and 
downloading that to always make it work with the latest browser.
   


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