erick-enriquez-dd opened a new issue, #22392:
URL: https://github.com/apache/superset/issues/22392

   A clear and concise description of what the bug is.
   Hi everyone, i'm trying to configure superset alerts and reporting (deployed 
on k8s) but i'm running into a bug when my alert tries to screenshot my chart. 
I'm running into ReportScheduleUnexpectedError message.
   
   #### How to reproduce the bug
   Enable an Alert in Alerts & Reports  to send a slack message with a 
screenshot of an existing Chart and view my logs in my worker node as the alert 
is scheduled. 
   
   ### Expected results
   A successful screenshot and message in slack
   ### Actual results
   I get the following error:
   
   `superset Scheduling alert Test2 eta: 2022-12-10 00:40:00                    
                                                                
   │ superset [2022-12-10 00:40:00,367: INFO/ForkPoolWorker-31] Scheduling 
alert Test2 eta: 2022-12-10 00:40:00                                            
 
   │ superset Query for Test2 took 170.06 ms                                    
                                                             
   │ superset [2022-12-10 00:40:00,751: INFO/ForkPoolWorker-31] Query for Test2 
took 170.06 ms                                                              
   │ superset Screenshotting chart at 
http://superset:8088/superset/slice/93/?standalone=true                         
                                         
   │ superset [2022-12-10 00:40:00,764: INFO/ForkPoolWorker-31] Screenshotting 
chart at http://superset:8088/superset/slice/93/?standalone=true                
                         
   │ superset Init selenium driver      
   │ superset [2022-12-10 00:40:00,767: INFO/ForkPoolWorker-31] Init selenium 
driver
   superset Taking a PNG screenshot or url 
http://superset:8088/superset/slice/93/?standalone=true&standalone=3            
                                                       
   │ superset [2022-12-10 00:40:11,678: INFO/ForkPoolWorker-31] Taking a PNG 
screenshot or url 
http://superset:8088/superset/slice/93/?standalone=true&standalone=3           
   │ superset (Background on this error at: http://sqlalche.me/e/13/2j85)       
                                                                      
   │ superset                                                                   
                                  
   │ superset During handling of the above exception, another exception 
occurred:                                                                       
  
   │ superset                                                                   
                                              
   │ superset Traceback (most recent call last):                                
                                                              
   │ superset  File "/app/superset/tasks/scheduler.py", line 71, in execute     
                                                                             
   │ superset   task_id, report_schedule_id, scheduled_dttm_,                   
                                                                      
   │ superset  File "/app/superset/reports/commands/execute.py", line 584, in 
run                                                                          
   │ superset   raise ReportScheduleUnexpectedError(str(ex))                    
                                                                
   │ superset 
superset.reports.commands.exceptions.ReportScheduleUnexpectedError: 
(psycopg2.errors.IdleInTransactionSessionTimeout) terminating connection due to 
idle-in-transaction timeout                      
   │ superset SSL connection has been closed unexpectedly`
   
   
   ### Environment
   Deployed on Kubernetes via helm charts.
   
   - browser type and version: chrome 108
   - superset version: 1.3.1
   - python version: 3.7.0
   - node.js version: not installed
   - any feature flags active:
   
   
   ### Checklist
   
   Make sure to follow these steps before submitting your issue - thank you!
   
   - [ ] I have checked the superset logs for python stacktraces and included 
it here as text if there are any.
   - [ ] I have reproduced the issue with at least the latest released version 
of superset.
   - [ ] 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]

Reply via email to