nigzak opened a new issue, #25284: URL: https://github.com/apache/superset/issues/25284
The email documentation for email alerts does not work anymore for chromium - probably since V115 (there was a change where chromium is stored since this date) => the docu should be updated #### How to reproduce the bug follow https://superset.apache.org/docs/installation/alerts-reports/ to set up chromium ### Problem Email does not work: - 1st issue: "stable" is not compatible with V102 in this howto - the howto is complete outdated - 2nd issue: since V115 the chromium is not able to be downloaded as explained, you cannot use LATEST_RELEASE_117 as example - 3rd issue: since V115 it seems the default folder of chromium unzip changed (there is a subfolder now) before V115 chromedriver unzip it was stored into /usr/bin/chromedriver after 115 is is unzip into /usr/bin/chromedriver-linux64/chromedriver If the folder is not MANUALLY changed (unzip and use subfolder) superset does not find the executable chromedriver files ``` // from docu 13.09.2023 RUN export CHROMEDRIVER_VERSION=$(curl --silent https://chromedriver.storage.googleapis.com/LATEST_RELEASE_102) && \ wget -q https://chromedriver.storage.googleapis.com/${CHROMEDRIVER_VERSION}/chromedriver_linux64.zip && \ unzip chromedriver_linux64.zip -d /usr/bin && \ chmod 755 /usr/bin/chromedriver && \ rm -f chromedriver_linux64.zip ``` ### Environment (please complete the following information): - browser type and version: chrome - superset version: 2.1.1 ### 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. ### fix for this issue This change does fix this behaviour - probably you can still improve it somehow if required/possible ``` RUN apt-get update && \ wget -q https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb && \ apt-get install -y --no-install-recommends ./google-chrome-stable_current_amd64.deb && \ rm -f google-chrome-stable_current_amd64.deb # refer https://googlechromelabs.github.io/chrome-for-testing/ RUN export CHROMEDRIVER_VERSION=$(curl --silent https://googlechromelabs.github.io/chrome-for-testing/LATEST_RELEASE_STABLE) && \ wget -q https://edgedl.me.gvt1.com/edgedl/chrome/chrome-for-testing/${CHROMEDRIVER_VERSION}/linux64/chromedriver-linux64.zip && \ unzip chromedriver-linux64.zip && \ mv chromedriver-linux64/* /usr/bin/ && \ chmod 755 /usr/bin/chromedriver && \ rm -f chromedriver-linux64.zip && \ rm -f -r chromedriver-linux64 ``` IT uses the new chrome-for-testing JSON api to get the current STABLE RELEASE which should match the CHROME_STABLE_RELEASE It unzips the folder (which is having a SUBFOLDER of "chromedriver-linux64" to the current dir Than it copies all files from this folder to /usr/bin and chmod the file to 755 than it deletes the zip + extracted folder again from current dir With this the report works again  -- 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]
