kerem-coemert opened a new issue, #32898:
URL: https://github.com/apache/superset/issues/32898

   ### Bug description
   
   Basically the same issue as #24014 and #25171 but I created this new issue 
as I do not have the permission to re-open closed issues.
   
   I use `docker-compose-non-dev.yml`. Once it completes, I create a new user 
via: `docker exec -it superset_app superset fab create-admin`. It works when I 
first login and I can see all the example graphs like the COVID-19 graph etc.
   
   But once I reopen the same frontend URL either from the same browser or 
through the private window, I get the exact same issue in my next login.
   
   I always have to run:
   
   ```
   docker compose -f docker/docker-compose.yml down -v --remove-orphans
   docker image ls | grep superset | awk '{print $3}' | xargs docker rmi -f
   ```
   
   and create the user again, before I can get the frontend working again. So 
clearly some resource gets corrupted in that second login.
   
   Looking forward to any help you could provide in this direction.
   
   
   ### Screenshots/recordings
   
   
![Image](https://github.com/user-attachments/assets/19d299f2-3bcb-4711-ab8f-f86b5a8a0790)
   
   ### Superset version
   
   master / latest-dev
   
   ### 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