Superset is not able to take the screenshot of the report and send it to mail

[Dhruvin4530]

Your report/alert was unable to be generated because of the following error: Failed taking a screenshot Message: Stacktrace: #0 0x563ca8753a6a #1 0x563ca8162ab5 #2 0x563ca81b5676 #3 0x563ca81b58b1 #4 0x563ca8200614 #5 0x563ca81fd7b6 #6 0x563ca81a8cbf #7 0x563ca81a9a81 #8 0x563ca8719a64 #9 0x563ca871c951 #10 0x563ca870621e #11 0x563ca871d51e #12 0x563ca86ecbe0 #13 0x563ca87409b8 #14 0x563ca8740b88 #15 0x563ca87524de #16 0x7f4ec2a3f1f5

Versions:

root@superset-5c86f589df-f54nd:/app# google-chrome --version
Google Chrome 146.0.7680.177 
root@superset-5c86f589df-f54nd:/app# chromedriver --version
ChromeDriver 146.0.7680.165 (4b989da09e15a7dc0de0785cb5ff232aadae3f0f-refs/branch-heads/7680@{#2932})
root@superset-5c86f589df-f54nd:/app# 

WEBDRIVER_TYPE = "chrome"
WEBDRIVER_OPTION_ARGS = [
    "--force-device-scale-factor=2.0",
    "--high-dpi-support=2.0",
    "--headless",
    "--disable-gpu",
    "--disable-dev-shm-usage",
    "--no-sandbox",
    "--disable-setuid-sandbox",
    "--disable-extensions",
]
# Window size - this will impact the rendering of the data
WEBDRIVER_WINDOW = {
    "dashboard": (1600, 2000),
    "slice": (3000, 1200),
    "pixel_density": 1,
}

[Dhruvin4530]

@dosu Could you please help?

[dosubot[bot]]

The issue is in how you're selecting the ChromeDriver version. Your script picks the last known-good version that matches the Chrome major version, but that's not guaranteed to match the exact patch version of google-chrome-stable. This is exactly why you ended up with Chrome 146.0.7680.177 but ChromeDriver 146.0.7680.165.

Instead of matching on just the major version, you should match on the full version (or at least the major.minor.build prefix like 146.0.7680). Here's a corrected approach:

RUN wget https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb \
    && apt install -y --no-install-recommends ./google-chrome-stable_current_amd64.deb \
    \
    && CHROME_VERSION=$(google-chrome --version | awk '{print $3}') \
    && CHROME_BUILD=$(echo $CHROME_VERSION | cut -d '.' -f 1-3) \
    && echo "Chrome version: $CHROME_VERSION, build prefix: $CHROME_BUILD" \
    \
    && DRIVER_URL=$(curl -s https://googlechromelabs.github.io/chrome-for-testing/known-good-versions-with-downloads.json \
       | jq -r --arg build "$CHROME_BUILD" \
       '.versions | map(select(.version | startswith($build + "."))) | last | .downloads.chromedriver[] | select(.platform=="linux64") | .url') \
    \
    && echo "Driver URL: $DRIVER_URL" \
    && test -n "$DRIVER_URL" \
    \
    && wget "$DRIVER_URL" -O chromedriver.zip \
    && unzip chromedriver.zip \
    && mv chromedriver-linux64/chromedriver /usr/bin/chromedriver \
    && chmod +x /usr/bin/chromedriver \
    \
    && rm -rf chromedriver-linux64 chromedriver.zip \
    && rm -f google-chrome-stable_current_amd64.deb \
    && apt clean \
    && google-chrome --version \
    && chromedriver --version

The key change is using cut -d '.' -f 1-3 (giving e.g. 146.0.7680) instead of just -f 1 (giving 146), so the ChromeDriver version closely matches Chrome's build number.

Alternatively, you can use the Chrome for Testing LATEST_PATCH_URL endpoint which gives you the exact matching ChromeDriver for a specific Chrome build:

CHROME_BUILD=$(google-chrome --version | awk '{print $3}' | cut -d '.' -f 1-3)
DRIVER_VERSION=$(curl -s "https://googlechromelabs.github.io/chrome-for-testing/LATEST_PATCH_VERSIONS_PER_BUILD_WITH_DOWNLOADS.json" \
  | jq -r --arg build "$CHROME_BUILD" '.builds[$build].downloads.chromedriver[] | select(.platform=="linux64") | .url')

This guarantees an exact patch-level match between Chrome and ChromeDriver.

That said, if you want to avoid these version-matching headaches entirely, consider switching to Playwright as mentioned earlier — it bundles its own browser binaries so there's no version mismatch to worry about.

To reply, just mention @dosu.

---

Docs are dead. Just use Dosu.

[Dhruvin4530]

This code is still giving the same.

12 15.60 Google Chrome 146.0.7680.177 
#12 15.61 ChromeDriver 146.0.7680.165 (4b989da09e15a7dc0de0785cb5ff232aadae3f0f-refs/branch-heads/7680@{#2932})
#12 DONE 15.8s

[Dhruvin4530]

@dosu

[Dhruvin4530]

@dosu
Here is my dockerfile, I am switching to playwright.

FROM apache/superset:5.0.0 AS test
# Switching to root to install the required packages
USER root
RUN apt-get update && apt-get install -y

# pysaml2 requirement
RUN apt-get install git xmlsec1 wget unzip jq -y

# Installing playwright & chromium
RUN uv pip install playwright \
    && playwright install --with-deps chromium

# https://lxml.de/installation.html
# RUN pip install lxml
# Example: installing the MySQL driver to connect to the metadata database
# if you prefer Postgres, you may want to use `psycopg2-binary` instead
RUN uv pip install "psycopg2-binary==2.9.1"
# Example: installing a driver to connect to Redshift
# Find which driver you need based on the analytics database
# you want to connect to here.
# Make sure the version is compatible and matches that which is set in
# https://github.com/apache/superset/blob/master/setup.py extras_require
# https://superset.apache.org/installation.html#database-dependencies
# RUN pip install "pyathena>=1.10.8, <1.11" "clickhouse-sqlalchemy>=0.1.4" pysaml2 statsd
# Update to the hydrolix rebased clickhouse-sqlalchemy to be compatible with new Superset version
RUN uv pip install git+https://github.com/sbdelisle/clickhouse-sqlalchemy@hdx-0.1.0 "pyathena>=1.10.8, <1.11" pysaml2 statsd "clickhouse-connect>=0.7.2" "cryptography>=42.0.4,<43.0.0"
# For Snowflake Integration
RUN uv pip install snowflake-sqlalchemy
# RUN pip install "python3-saml" # Some dependency issues here? :thinking:
# Copy over custom assets
COPY /assets/superset-logo-horiz-arkose-logo.png /app/superset/static/assets/images/superset-logo-horiz-arkose.png
COPY /assets/superset-logo-horiz-arkose-logo2.png /app/superset/static/assets/images/superset-logo-horiz-arkose2.png
COPY /assets/ArkoseLabs_BLACK_Vertical.png /app/superset/static/assets/images/arkoselabs-black.png
# Copy over custom templates
COPY /templates/sso_logout.html /app/superset/templates/arkose/sso_logout.html
COPY /templates/unauthorized.html /app/superset/templates/arkose/unauthorized.html
# Copy scripts 
COPY /scripts/utils.py superset/commands/importers/v1/utils.py
# Copy over certificates
COPY /tmp/certs/ /app/config/certs/
COPY /assets/certs/us-east-2-bundle.pem /usr/lib/ssl/certs 
# Switching back to using the `superset` user
USER superset

Is this good?

[dosubot[bot]]

The Dockerfile looks good for installing Playwright and Chromium. A couple of things to make sure of:

1. Add the config flag in your superset_config.py to actually enable Playwright:

PLAYWRIGHT_REPORTS_AND_THUMBNAILS = True

Without this, Superset will still try to use Selenium even though Playwright is installed [1].

2. Optional tuning — you can adjust timeouts if needed [2]:

SCREENSHOT_PLAYWRIGHT_DEFAULT_TIMEOUT = 60000  # milliseconds
SCREENSHOT_PLAYWRIGHT_WAIT_EVENT = "load"  # or "networkidle" for heavier dashboards

3. Memory — make sure your worker container has at least 1–2 GB of memory. Chromium will silently fail to start if resources are too low [3].

4. Quick sanity check — after building, you can verify Playwright works inside the container by running:

playwright screenshot http://localhost:8088/ /tmp/test.png

If that fails, it usually means missing system dependencies [3].

You can also remove all the old Chrome/ChromeDriver-related lines from your Dockerfile since they're no longer needed with Playwright.

To reply, just mention @dosu.

---

Docs are dead. Just use Dosu.

[Dhruvin4530]

@dosu This is not sending full screenshot

[dosubot[bot]]

It looks like the screenshot is being cut off because the dashboard content exceeds the configured viewport height. Superset captures a specific HTML element within the browser viewport — it does not scroll or dynamically measure the full page height [1]. So anything taller than your configured window size gets truncated.

A few things to try:

1. Increase the dashboard viewport height — Your current WEBDRIVER_WINDOW sets the dashboard viewport to 1600×2000. If your dashboard is taller than 2000px, increase the height:

WEBDRIVER_WINDOW = {
    "dashboard": (1600, 4000),  # increase height to fit your dashboard
    "slice": (3000, 1200),
    "pixel_density": 1,
}

2. Increase load wait times — If some charts haven't finished rendering before the screenshot is captured, they'll appear blank. Increase these timeouts [2]:

SCREENSHOT_LOCATE_WAIT = 30   # default is 10 seconds
SCREENSHOT_LOAD_WAIT = 120    # default is 60 seconds

3. Enable tiled screenshots (if available in your version) — For large dashboards, Superset has a tiled screenshot feature that captures multiple viewport-sized sections and stitches them together (PR #34561). This is the best solution for dashboards with many rows:

SCREENSHOT_TILED_ENABLED = True

4. Also note — you have --force-device-scale-factor=2.0 and --high-dpi-support=2.0 in your webdriver args but pixel_density set to 1. This mismatch could cause sizing issues. Either remove those Chrome flags or set pixel_density to 2 to keep them consistent [3].

To reply, just mention @dosu.

---

Share context across your team and agents. Try Dosu.

[Dhruvin4530]

@dosu My dashboards are very lengthy in size and I have set "dashboard": (1600, 6000, is there any other option which can fit for all kinds of dashboards?

[dosubot[bot]]

Since you've already switched to Playwright, the best option for handling dashboards of varying heights is the tiled screenshot feature, which is available in Superset 5.0+ [1]. It automatically divides tall dashboards into multiple viewport-sized tiles and stitches them into a single image — so you don't need to guess a viewport height.

It's actually enabled by default, but you can tune the thresholds in your superset_config.py [2]:

SCREENSHOT_TILED_ENABLED = True                  # enabled by default
SCREENSHOT_TILED_HEIGHT_THRESHOLD = 5000          # trigger tiling if dashboard is taller than 5000px
SCREENSHOT_TILED_VIEWPORT_HEIGHT = 2000           # height of each captured tile

With this, you can set your WEBDRIVER_WINDOW dashboard height back to a reasonable value (e.g., (1600, 2000)), and the tiling logic will automatically kick in for dashboards that exceed the height threshold — no need to hardcode a very large number.

Important: This feature is Playwright-only — it does not work with Selenium. So make sure you have PLAYWRIGHT_REPORTS_AND_THUMBNAILS = True set.

To reply, just mention @dosu.

---

Share context across your team and agents. Try Dosu.

[Dhruvin4530]

@dosu If I use this SCREENSHOT_TILED_ENABLED = True then do I need

WEBDRIVER_WINDOW = {
    "dashboard": (1600, 6000),
    "slice": (3000, 1200),
    "pixel_density": 1,
}

?

[dosubot[bot]]

You still need WEBDRIVER_WINDOW, but you don't need the large 6000 height anymore. WEBDRIVER_WINDOW still controls the initial browser viewport size even with tiling enabled [1]. The tiling feature handles the full capture by scrolling the page in increments of SCREENSHOT_TILED_VIEWPORT_HEIGHT and stitching tiles together [2].

So you can use a normal height:

WEBDRIVER_WINDOW = {
    "dashboard": (1600, 2000),
    "slice": (3000, 1200),
    "pixel_density": 1,
}

SCREENSHOT_TILED_ENABLED = True
SCREENSHOT_TILED_HEIGHT_THRESHOLD = 5000     # trigger tiling for dashboards taller than this
SCREENSHOT_TILED_VIEWPORT_HEIGHT = 2000      # height of each tile

One thing to note: there's a reported issue where SCREENSHOT_TILED_VIEWPORT_HEIGHT being larger than the actual browser viewport height can cause content gaps between tiles [3]. If you see gaps in the stitched image, try setting SCREENSHOT_TILED_VIEWPORT_HEIGHT to match or be smaller than your WEBDRIVER_WINDOW dashboard height.

Also remember that tiling only kicks in when the dashboard exceeds the SCREENSHOT_TILED_HEIGHT_THRESHOLD (default 5000px). Shorter dashboards will still use a single screenshot with your WEBDRIVER_WINDOW dimensions.

To reply, just mention @dosu.

---

Share context across your team and agents. Try Dosu.