SekelPrem opened a new issue, #24922: URL: https://github.com/apache/superset/issues/24922
Following the docker-compose for non dev, configured it locally on Mac OSX, I was unable to get the reports to my email even after setting up the SMTP setting #### How to reproduce the bug 1. Go to 'https://superset.apache.org/docs/installation/installing-superset-using-docker-compose' 2. Follow the setup to install and run the Apache super set using the docker 3. Enabling Alerts and Reports features with Redis, celery_best schedule, and other configurations as specified in the setup 4. After setting up reports for a sample or custom-created chart I see the below errors. ### Expected results 1. email to be recieved what you expected to happen. ### Actual results Errors what actually happens. #### Screenshots Since I was receiving gecko-driver errors, I tried to install them in requirement.txt but it din't work, please let me know what to be added in requirements txt so that gecko-driver is installed, <img width="1440" alt="image" src="https://github.com/apache/superset/assets/119047771/d6706c67-6f1e-4475-a660-dd472f237153";> <img width="1433" alt="image" src="https://github.com/apache/superset/assets/119047771/e270bb54-f30d-4009-b57e-4592d81105e3";> ### Environment (please complete the following information): - browser type and version: chrome - superset version: `superset version` 2.1.0 - python version: `python --version` 3.8 - node.js version: `node -v` docker node - any feature flags active: Alerts and Reports ### Checklist Make sure to follow these steps before submitting your issue - thank you! - [ Yes ] I have checked the superset logs for python stacktraces and included it here as text if there are any. - [ Yes ] I have reproduced the issue with at least the latest released version of superset. - [ Yes ] I have checked the issue tracker for the same issue and I haven't found one similar. ### Additional context Add any other context about the problem here. -- 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]
