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

   ### Bug description
   
   While experimenting with Treemap charts in the Explore view, clicking the 
“Samples” tab triggers a request to "/datasource/samples". The backend responds 
with HTTP 200 but an empty body. The frontend loader spins for some time, and 
then the UI freezes.
   
   STEPS TO REPRODUCE IT: 
   
   1- Run Superset in Docker (latest dev build - Docker Compose).
   2- Go to the charts tab and create a Treemap chart using any dataset.
   3- Click the “Samples” tab (bottom right).
   4- Observe loader spins, UI freezes, and no data shown.
   
   Expected Behavior:
   The Samples tab should display rows or show a “No data available” message or 
something like that.
   
   Actual Behavior:
   The UI freezes after receiving a 200 response with no content.
   
   
   ### Screenshots/recordings
   
   <img width="1914" height="956" alt="Image" 
src="https://github.com/user-attachments/assets/d7720c6e-feb2-46ec-b5fe-01020f41034d";
 />
   
   
   HERE IS THE SCREEN RECORDING OF THAT EXACT ISSUE : 
   
   
https://github.com/user-attachments/assets/2423b73e-52de-410e-9102-5bf4d67b04e6
   
   ### Superset version
   
   master / latest-dev
   
   ### Python version
   
   3.11
   
   ### Node version
   
   18 or greater
   
   ### Browser
   
   Chrome
   
   ### Additional context
   
   Any Dataset will give the same response. I have checked it multiple times.
   
   Backend log snippet : 
   POST /datasource/samples?force=false&datasource_type=table&datasource_id=1 
HTTP/1.1" 200 -
   
   ### 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