nathan-gilbert opened a new issue, #27952:
URL: https://github.com/apache/superset/issues/27952

   ### Bug description
   
   Problem is the title. No matter what timezone I select, the report job gets 
scheduled 12 hours ahead. 
   
   In the Superset UI, the timezone display on the created report job is always 
different than what I selected in the UI (which is typically, GMT -6):
   
![image](https://github.com/apache/superset/assets/546222/0d5f4ac9-5481-4f86-98e1-4c35a4902796)
   
   In flower, I can see the jobs and their ETA looks correct but the job 
doesn't get executed then, but exactly 12 hours later:
   
![image](https://github.com/apache/superset/assets/546222/3eeb3d4b-dabf-4590-b8a9-8bde9d241807)
   
   I'm running Superset/Celery on a Ubuntu 22.04, Python 3.11. Not in docker, 
just directly. 
   
   Here's my celery config:
   ```python
   class CeleryConfig:
       """
       Celery worker configuration
       """
   
       broker_url = f"redis://{REDIS_HOST}:{REDIS_PORT}/0"
       imports = (
           "superset.sql_lab",
           "superset.tasks.scheduler",
       )
       result_backend = f"redis://{REDIS_HOST}:{REDIS_PORT}/0"
       worker_prefetch_multiplier = 10
       task_protocol = 2
       task_acks_late = True
       task_annotations = {
           "sql_lab.get_sql_results": {
               "rate_limit": "100/s",
           },
           "tasks.add": {
               "rate_limit": "10/s",
           },
           "email_reports.send": {
               "rate_limit": "1/s",
               "time_limit": 120,
               "soft_time_limit": 150,
               "ignore_result": True,
           },
       }
       beat_schedule = {
           "reports.scheduler": {
               "task": "reports.scheduler",
               "schedule": crontab(minute="*", hour="*"),
           },
           "reports.prune_log": {
               "task": "reports.prune_log",
               "schedule": crontab(minute="0", hour="0"),
           },
       }
       timezone = "America/Denver"
       enable_utc = False
   ```
   
   ### How to reproduce the bug
   
   Turn on Alerts/reports. 
   
   Add new report, select GMT -6 as the timezone. Create the job. See in the 
worker logs that the job wont execute for another 12 hours. 
   
   ### Screenshots/recordings
   
   Celery worker logs:
   
![image](https://github.com/apache/superset/assets/546222/b31205a1-3607-4083-87a6-cf815f54c6a0)
   
   
   ### Superset version
   
   3.1.2
   
   ### Python version
   
   3.11
   
   ### Node version
   
   Not applicable
   
   ### Browser
   
   Chrome
   
   ### Additional context
   
   _No response_
   
   ### Checklist
   
   - [X] I have searched Superset docs and Slack and didn't find a solution to 
my problem.
   - [X] I have searched the GitHub issue tracker and didn't find a similar bug 
report.
   - [X] I have checked Superset's logs for errors and if I found a relevant 
Python stacktrace, I included it here as text in the "additional context" 
section.


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