chrisvnimbus opened a new issue, #31906: URL: https://github.com/apache/superset/issues/31906
### Bug description When using the Download -> Save as image button while viewing a chart, everything works fine and the image is created without trouble. However, when using the Download -> Save as Image or Save as PDF button in a dashboard view, the command fails, and on the backend there is a logged attempt at accessing a SQLite file ((sqlite3.OperationalError) unable to open database file). The configured storage for superset metadata is a Postgres DB however. It is unclear to me why the Save As Image functionality on a chart level tries to refer to a different database than the same functionality at a Dashboard level, and why the latter would attempt to rely on SQLite even though the configured database in the config file is a Postgres DB. When scouring this GitHub, the only reference I could find is [here](https://github.com/apache/superset/discussions/30820), on a discussion of the error occuring in 4.1.0rc3 but not in4.1.0rc4. I can not find a specific topic for the issue however, and I'm not sure why it is affecting my 4.0 build. ### Screenshots/recordings _No response_ ### Superset version 4.0.2 ### Python version 3.9 ### Node version 18 or greater ### Browser Chrome ### Additional context Jan 17, 2025, 3:26:40 PM None 2025-01-17 14:26:40,024:ERROR:flask_appbuilder.api:(sqlite3.OperationalError) unable to open database file - Jan 17, 2025, 3:26:40 PM None 2025-01-17 14:26:40,022:INFO:superset.dashboards.api:Triggering screenshot ASYNC - ### 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]
