lodu opened a new issue, #25459:
URL: https://github.com/apache/superset/issues/25459

   In config.py a EMAIL_NOTIFICATIONS with comment "all the emails are sent 
using dryrun" can be set. This has no effect, since it is called nowhere in the 
codebase. I expect there to be a dryrun option for e.g. some outward facing dev 
environments.
   
   #### How to reproduce the bug
   
   1. In `config.py` set `EMAIL_NOTIFICATIONS = False`
   2. Create a new email report
   3. Trigger email report
   
   ### Expected results
   1. No Mail is received
   
   ### Actual results
   
   1. Mail is received
   
   #### Screenshots
   
![image](https://github.com/apache/superset/assets/48859312/326d7e6f-db68-49bd-aca6-f00d371c24ae)
   As seen in screenshot: it just says `dryrun = False` and not requesting said 
config option.
   
   
   
   ### Environment
   - firefox (v117.0.1 64-bit) 
   - superset 3.0.0 Docker image (prod version not rc)
     - also on the current master branch (I git cloned and ran locally)
   - any feature flags active: ALERT_REPORTS
   
   ### Checklist
   - [ x] I have reproduced the issue with at least the latest released version 
of superset.
   
   ### Additional context
   
   [Slack conversation about 
it](https://apache-superset.slack.com/archives/C015WAZL0KH/p1695972330191929)
   


-- 
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: notifications-unsubscr...@superset.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org
For additional commands, e-mail: notifications-h...@superset.apache.org

Reply via email to