Narendra678 opened a new issue #17558:
URL: https://github.com/apache/superset/issues/17558


   A clear and concise description of what the bug is.
   
   #### How to reproduce the bug
   Getting Unexpected error as below:
   
   <html><head> <meta http-equiv="content-type" 
content="text/html;charset=utf-8"> <title>500 Server Error</title> </head> 
<body text=#000000 bgcolor=#ffffff> <h1>Error: Server Error</h1> <h2>The server 
encountered an error and could not complete your request.<p>Please try again in 
30 seconds.</h2> <h2></h2> </body></html>
   
   ### Expected results
   Should show data
   what you expected to happen.
   
   
![image](https://user-images.githubusercontent.com/88739186/143541581-711b020e-74c9-4399-94eb-9f6c6a7e0707.png)
   
   
   From past 5 days we are working on this but no luck. And it is happening 
some times.
   
   
   ### Environment
   
   (please complete the following information):
   
   - browser type and version:
   - superset version: `superset version`: 1.3.1
   - python version: `python --version`
   - node.js version: `node -v`
   - 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