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

   ### Bug description
   
   This issue happened after upgrading from version 3.0.1 to 4.1.2
   
   ### Screenshots/recordings
   
   
![Image](https://github.com/user-attachments/assets/f6cd50e9-b18e-4bbe-852a-2433d99220f6)
   
![Image](https://github.com/user-attachments/assets/d8c2a994-81c7-4d34-9f32-aeed077bcf89)
   
   ### Superset version
   
   4.1.2
   
   ### Python version
   
   3.10
   
   ### Node version
   
   I don't know
   
   ### Browser
   
   Chrome
   
   ### Additional context
   
   Config.py
   
   ```
   ROW_LIMIT = 5000
   
   # Generate a new key using "openssl rand -base64 42" and restart the server
   SECRET_KEY = "removed_for_this_post"
   
   # The SQLAlchemy connection string to your database backend
   SQLALCHEMY_DATABASE_URI = 
'mysql+mysqlconnector://some:SOME@SOME:3306/superset?charset=utf8mb4&ssl_disabled=True'
   
   
   # Basic configuration for http. Change and secure in https production 
environment
   TALISMAN_ENABLED = False
   WTF_CSRF_ENABLED = False
   
   ENABLE_PROXY_FIX=True
   ```
   
   The error is on the api
   
   ### 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