Open Jkraft7 opened 1 year ago
We also noticed the same issue while testing 3.0.0 version.
Thanks for confirming this was happening in 3.0.0. Is it still in 3.1.x or 4.0? I assume so, but it's been quite a while since nay updates happened here, so I want to make sure this still valid before it becomes at risk of being closed as stale. ALso have you tried the PLAYWRIGHT_REPORTS_AND_THUMBNAILS
flag?
Hi, we are facing similar issue. caching the dashboard before the report is generated should help in these type of scenario.
In our superset instance we use celery workers to get thumbnails. We run into an issue where if there is an empty/blank dashboard that exists. It causes selenium errors to continually occur whenever the thumbnail is attempted to be created in the celery worker which leads to massive cpu usage and blockers for other things (such as reports/alerts)
It states selenium is timing out while trying to run the get_screenshot function. the error itself is:
This error began occurring after the upgrade from 2.0.0 to 2.1.0. This can be detrimental to a celery worker as if there are not enough threads plus the users generate multiple blank/empty dashboards this can block all other activity in the celery worker.
From my perspective it is exactly related to this: https://github.com/apache/superset/issues/17245 except this is when we try to generate a thumbnail and not a report. These two functionalities should be running roughly the same logic i believe. As a note on that i can also replicate the above issue in my environment as well.
How to reproduce the bug
Expected results
Expect that the dashboard will just generate a blank screenshot or have some form of a default method to handle empty dashboards instead of throwing an error consistently.
Actual results
Error is thrown every time selenium attempts to screenshot the dashboard for the thumbnail
Screenshots
Environment
(please complete the following information):
2.1.0
3.8.16-slim
16-slim
Allow for javascript controls components
}
Checklist
Make sure to follow these steps before submitting your issue - thank you!
Additional context
Add any other context about the problem here.