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

   ### Bug description
   
   This is the 3.1.2 iteration of the this 
[issue](https://github.com/apache/superset/issues/23959)
   While using the superset app, I sometimes face two issues which might be 
related:
   - The superset app is stuck on the loading screen until refreshed manually.
   - When a dashboard is opened it gives an unexpected error.
   
   ### How to reproduce the bug
   
   Host the latest version of the superset app deployed using docker, in an EC2 
instance.
   Connect the superset with a database and create multiple dashboards.
   Use it continuously for a while. In our case this issue can be raised after 
the redeployment process.
   
   
   ### Screenshots/recordings
   
   SQL Lab example:
   
![chunkerr1](https://github.com/apache/superset/assets/12499311/f6b15e01-0209-471e-90dd-86aacb665f92)
   Dashboards tab example:
   
![chunkerr2](https://github.com/apache/superset/assets/12499311/499bf964-f393-4f31-9a5c-81b9d8397851)
   
   
   ### Superset version
   
   3.1.2
   
   ### Python version
   
   3.9
   
   ### Node version
   
   16
   
   ### 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