You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "Vitor-Avila (via GitHub)" <gi...@apache.org> on 2026/06/18 22:59:42 UTC

[PR] fix(chart API): apply dashboard filters by live scope, not stale chartsInScope [superset]

Vitor-Avila opened a new pull request, #41214:
URL: https://github.com/apache/superset/pull/41214

   ### SUMMARY
   When a chart's data/query is fetched with `filters_dashboard_id` (`GET /api/v1/chart/<id>/data/?filters_dashboard_id=<id>`), some dashboard filters were not properly applied. The current logic was relying on `chartsInScope`, which is recomputed on every load, so could be stale. This PR updates the logic to rely on `scope` (`rootPath` / `excluded`) instead.
   
   I believe the actual root-cause for stale/incorrect `chartsInScope` values might have been already fixed (for example with https://github.com/apache/superset/pull/38171) but this PR ensures dashboards in this state also work properly with this API endpoint.
   
   ### BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
   No UI changes.
   
   ### TESTING INSTRUCTIONS
   Test coverage updated. For manual testing:
   1. Add a chart to a dashboard with default filter. 
   2. Make sure the filter is scoped to all charts, but intentionally remove the chart ID from `chartsInScope`.
   3. Validate the filter still works properly via the UI.
   4. Send a `GET` to `/api/v1/chart/<id>/data/?filters_dashboard_id=<id>` and confirm the query/data also includes the filter.
   
   ### ADDITIONAL INFORMATION
   <!--- Check any relevant boxes with "x" -->
   <!--- HINT: Include "Fixes #nnn" if you are fixing an existing issue -->
   - [ ] Has associated issue:
   - [ ] Required feature flags:
   - [ ] Changes UI
   - [ ] Includes DB Migration (follow approval process in [SIP-59](https://github.com/apache/superset/issues/13351))
     - [ ] Migration is atomic, supports rollback & is backwards-compatible
     - [ ] Confirm DB migration upgrade and downgrade tested
     - [ ] Runtime estimates and downtime expectations provided
   - [ ] Introduces new feature or API
   - [ ] Removes existing feature or API
   


-- 
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: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org


Re: [PR] fix(chart API): apply dashboard filters by live scope, not stale chartsInScope [superset]

Posted by "rusackas (via GitHub)" <gi...@apache.org>.
rusackas commented on PR #41214:
URL: https://github.com/apache/superset/pull/41214#issuecomment-4752984931

   Thanks @Vitor-Avila, ths all seems sensible, but `unit-tests` ned some love. Those fixtures have `chartsInScope` but no `scope`/layout, so once we stop honoring `chartsInScope` the filter falls through to `"ROOT_ID" in []` and gets dropped. Is that just stale test data, or do real configs ever ship `chartsInScope` without a usable `scope.rootPath`? Want to make sure we're not silently dropping filters in the MCP path before this goes in.


-- 
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: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org


Re: [PR] fix(chart API): apply dashboard filters by live scope, not stale chartsInScope [superset]

Posted by "bito-code-review[bot] (via GitHub)" <gi...@apache.org>.
bito-code-review[bot] commented on PR #41214:
URL: https://github.com/apache/superset/pull/41214#issuecomment-4747145749

   <!-- Bito Reply -->
   The observation is correct. By removing the `chartsInScope` check entirely, the function now relies solely on the `scope` dictionary. If `scope` is missing or malformed (e.g., not a dictionary), `scope.get("rootPath", [])` defaults to an empty list, causing the filter to be incorrectly excluded for all charts. Using `chartsInScope` as a fallback when `scope` is missing or invalid would preserve backward compatibility for older dashboard metadata while still allowing the intended fix for stale cache issues.
   
   **superset/charts/data/dashboard_filter_context.py**
   ```
   scope = filter_config.get("scope")
       if isinstance(scope, dict):
           root_path: list[str] = scope.get("rootPath", [])
           excluded: list[int] = scope.get("excluded", [])
       else:
           # Fallback to chartsInScope if scope is missing or invalid
           charts_in_scope = filter_config.get("chartsInScope")
           if isinstance(charts_in_scope, list):
               return chart_id in charts_in_scope
           return False
   ```


-- 
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: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org


Re: [PR] fix(chart API): apply dashboard filters by live scope, not stale chartsInScope [superset]

Posted by "bito-code-review[bot] (via GitHub)" <gi...@apache.org>.
bito-code-review[bot] commented on PR #41214:
URL: https://github.com/apache/superset/pull/41214#issuecomment-4746829798

   AI Code Review is in progress (usually takes 3 to 15 minutes unless it's a very large PR).


-- 
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: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org


Re: [PR] fix(chart API): apply dashboard filters by live scope, not stale chartsInScope [superset]

Posted by "bito-code-review[bot] (via GitHub)" <gi...@apache.org>.
bito-code-review[bot] commented on PR #41214:
URL: https://github.com/apache/superset/pull/41214#issuecomment-4754701392

   **Bito Automatic Review Skipped – PR Already Merged**<br/><br/>Bito scheduled an automatic review for this pull request, but the review was skipped because this PR was merged before the review could be run.<br/>No action is needed if you didn't intend to review it. To get a review, you can type `/review` in a comment and save it


-- 
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: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org


Re: [PR] fix(chart API): apply dashboard filters by live scope, not stale chartsInScope [superset]

Posted by "Copilot (via GitHub)" <gi...@apache.org>.
Copilot commented on code in PR #41214:
URL: https://github.com/apache/superset/pull/41214#discussion_r3439579417


##########
superset/charts/data/dashboard_filter_context.py:
##########
@@ -107,8 +98,7 @@ def _is_filter_in_scope_for_chart(
 
     # If the chart doesn't exist in the dashboard layout, treat it as a
     # root-level chart.
-    else:
-        return "ROOT_ID" in root_path
+    return "ROOT_ID" in root_path

Review Comment:
   `_is_filter_in_scope_for_chart` now ignores `chartsInScope` unconditionally, but some call sites/fixtures (and potentially older dashboard metadata) provide `chartsInScope` without a `scope` object. In that case `rootPath` defaults to `[]` and the filter becomes out-of-scope for every chart, which is a behavioral regression unrelated to the “stale cache” fix. Consider using `chartsInScope` only as a backwards-compatibility fallback when `scope` is missing or not a dict.



-- 
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: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org


Re: [PR] fix(chart API): apply dashboard filters by live scope, not stale chartsInScope [superset]

Posted by "Vitor-Avila (via GitHub)" <gi...@apache.org>.
Vitor-Avila commented on code in PR #41214:
URL: https://github.com/apache/superset/pull/41214#discussion_r3443845070


##########
superset/charts/data/dashboard_filter_context.py:
##########
@@ -107,8 +98,7 @@ def _is_filter_in_scope_for_chart(
 
     # If the chart doesn't exist in the dashboard layout, treat it as a
     # root-level chart.
-    else:
-        return "ROOT_ID" in root_path
+    return "ROOT_ID" in root_path

Review Comment:
   `chartsInScope` is a denormalized cache derived from scope [ref](https://github.com/apache/superset/blob/master/superset-frontend/src/dashboard/util/calculateScopes.ts#L58-L62) (the type definition for `scope` is required, but for `chartsInScope` is optional [ref](https://github.com/apache/superset/blob/master/superset-frontend/packages/superset-ui-core/src/query/types/Dashboard.ts#L67-L90)). That said, we should always have a `scope` value (the app can't produce `chartsInScope` without a `scope`).
   
   The frontend does read `chartsInScope`, but it recomputes it from `scope` on every load before using it [ref](https://github.com/apache/superset/blob/master/superset-frontend/src/dashboard/components/DashboardBuilder/DashboardContainer.tsx#L203-L225), so `scope` is the real source of truth and the saved cache is never trusted as-is. The gap is that this recompute lives in memory and is only persisted on an explicit save, so the stored `chartsInScope` drifts stale while the UI stays correct. 
   
   With that in mind, computing from `scope` (what this PR does, mirroring `calculateScopes`/`getChartIdsInFilterScope`) is the backend equivalent of the frontend's recompute.



-- 
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: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org


Re: [PR] fix(chart API): apply dashboard filters by live scope, not stale chartsInScope [superset]

Posted by "Vitor-Avila (via GitHub)" <gi...@apache.org>.
Vitor-Avila merged PR #41214:
URL: https://github.com/apache/superset/pull/41214


-- 
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: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org


Re: [PR] fix(chart API): apply dashboard filters by live scope, not stale chartsInScope [superset]

Posted by "Vitor-Avila (via GitHub)" <gi...@apache.org>.
Vitor-Avila commented on code in PR #41214:
URL: https://github.com/apache/superset/pull/41214#discussion_r3443845070


##########
superset/charts/data/dashboard_filter_context.py:
##########
@@ -107,8 +98,7 @@ def _is_filter_in_scope_for_chart(
 
     # If the chart doesn't exist in the dashboard layout, treat it as a
     # root-level chart.
-    else:
-        return "ROOT_ID" in root_path
+    return "ROOT_ID" in root_path

Review Comment:
   `chartsInScope` is a denormalized cache derived from scope [ref](https://github.com/apache/superset/blob/master/superset-frontend/src/dashboard/util/calculateScopes.ts#L58-L62) (the type definition for `scope` is required, but for `chartsInScope` is optional [ref](https://github.com/apache/superset/blob/master/superset-frontend/packages/superset-ui-core/src/query/types/Dashboard.ts#L67-L90)). That said, we should always have a `scope` value (the app can't produce `chartsInScope` without a `scope`).
   
   The frontend does read `chartsInScope`, but it recomputes it from `scope` on every load before using it [ref](https://github.com/apache/superset/blob/master/superset-frontend/src/dashboard/components/DashboardBuilder/DashboardContainer.tsx#L203-L225), so `scope` is the real source of truth and the saved cache is never trusted as-is. The gap is that this recompute lives in memory and is only persisted on an explicit save, so the stored `chartsInScope` drifts stale while the UI stays correct. 
   
   With that in mind, computing from scope (what this PR does, mirroring `calculateScopes`/`getChartIdsInFilterScope`) is the backend equivalent of the frontend's recompute.



-- 
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: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org


Re: [PR] fix(chart API): apply dashboard filters by live scope, not stale chartsInScope [superset]

Posted by "Vitor-Avila (via GitHub)" <gi...@apache.org>.
Vitor-Avila commented on PR #41214:
URL: https://github.com/apache/superset/pull/41214#issuecomment-4753578776

   > Thanks @Vitor-Avila, ths all seems sensible, but `unit-tests` ned some love. Those fixtures have `chartsInScope` but no `scope`/layout, so once we stop honoring `chartsInScope` the filter falls through to `"ROOT_ID" in []` and gets dropped. Is that just stale test data, or do real configs ever ship `chartsInScope` without a usable `scope.rootPath`? Want to make sure we're not silently dropping filters in the MCP path before this goes in.
   
   I think the concern here is very valid, @rusackas. My response to the bot comment might also be applicable here:
   
   > `chartsInScope` is a denormalized cache derived from scope [ref](https://github.com/apache/superset/blob/master/superset-frontend/src/dashboard/util/calculateScopes.ts#L58-L62) (the type definition for `scope` is required, but for `chartsInScope` is optional [ref](https://github.com/apache/superset/blob/master/superset-frontend/packages/superset-ui-core/src/query/types/Dashboard.ts#L67-L90)). That said, we should always have a `scope` value (the app can't produce `chartsInScope` without a `scope`).
   > 
   > The frontend does read `chartsInScope`, but it recomputes it from `scope` on every load before using it [ref](https://github.com/apache/superset/blob/master/superset-frontend/src/dashboard/components/DashboardBuilder/DashboardContainer.tsx#L203-L225), so `scope` is the real source of truth and the saved cache is never trusted as-is. The gap is that this recompute lives in memory and is only persisted on an explicit save, so the stored `chartsInScope` drifts stale while the UI stays correct.
   > 
   > With that in mind, computing from scope (what this PR does, mirroring `calculateScopes`/`getChartIdsInFilterScope`) is the backend equivalent of the frontend's recompute.
   
   


-- 
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: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org


Re: [PR] fix(chart API): apply dashboard filters by live scope, not stale chartsInScope [superset]

Posted by "codecov[bot] (via GitHub)" <gi...@apache.org>.
codecov[bot] commented on PR #41214:
URL: https://github.com/apache/superset/pull/41214#issuecomment-4746853020

   ## [Codecov](https://app.codecov.io/gh/apache/superset/pull/41214?dropdown=coverage&src=pr&el=h1&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) Report
   :x: Patch coverage is `0%` with `1 line` in your changes missing coverage. Please review.
   :white_check_mark: Project coverage is 55.62%. Comparing base ([`76e2418`](https://app.codecov.io/gh/apache/superset/commit/76e2418f1eab7efd915f7cf335336e5c18bb7ed3?dropdown=coverage&el=desc&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache)) to head ([`494af99`](https://app.codecov.io/gh/apache/superset/commit/494af990e48c0b567820c002a5cb4ffc6e29aa95?dropdown=coverage&el=desc&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache)).
   :warning: Report is 10 commits behind head on master.
   
   | [Files with missing lines](https://app.codecov.io/gh/apache/superset/pull/41214?dropdown=coverage&src=pr&el=tree&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) | Patch % | Lines |
   |---|---|---|
   | [superset/charts/data/dashboard\_filter\_context.py](https://app.codecov.io/gh/apache/superset/pull/41214?src=pr&el=tree&filepath=superset%2Fcharts%2Fdata%2Fdashboard_filter_context.py&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache#diff-c3VwZXJzZXQvY2hhcnRzL2RhdGEvZGFzaGJvYXJkX2ZpbHRlcl9jb250ZXh0LnB5) | 0.00% | [1 Missing :warning: ](https://app.codecov.io/gh/apache/superset/pull/41214?src=pr&el=tree&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) |
   > :exclamation:  There is a different number of reports uploaded between BASE (76e2418) and HEAD (494af99). Click for more details.
   > 
   > <details><summary>HEAD has 6 uploads less than BASE</summary>
   >
   >| Flag | BASE (76e2418) | HEAD (494af99) |
   >|------|------|------|
   >|python|8|2|
   ></details>
   
   <details><summary>Additional details and impacted files</summary>
   
   
   
   ```diff
   @@            Coverage Diff             @@
   ##           master   #41214      +/-   ##
   ==========================================
   - Coverage   64.33%   55.62%   -8.71%     
   ==========================================
     Files        2651     2651              
     Lines      144784   144784              
     Branches    33406    33405       -1     
   ==========================================
   - Hits        93140    80536   -12604     
   - Misses      49976    63514   +13538     
   + Partials     1668      734     -934     
   ```
   
   | [Flag](https://app.codecov.io/gh/apache/superset/pull/41214/flags?src=pr&el=flags&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) | Coverage Δ | |
   |---|---|---|
   | [hive](https://app.codecov.io/gh/apache/superset/pull/41214/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) | `39.32% <0.00%> (ø)` | |
   | [mysql](https://app.codecov.io/gh/apache/superset/pull/41214/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) | `?` | |
   | [postgres](https://app.codecov.io/gh/apache/superset/pull/41214/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) | `?` | |
   | [presto](https://app.codecov.io/gh/apache/superset/pull/41214/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) | `40.91% <0.00%> (+<0.01%)` | :arrow_up: |
   | [python](https://app.codecov.io/gh/apache/superset/pull/41214/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) | `40.97% <0.00%> (-18.60%)` | :arrow_down: |
   | [sqlite](https://app.codecov.io/gh/apache/superset/pull/41214/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) | `?` | |
   | [unit](https://app.codecov.io/gh/apache/superset/pull/41214/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) | `?` | |
   
   Flags with carried forward coverage won't be shown. [Click here](https://docs.codecov.io/docs/carryforward-flags?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache#carryforward-flags-in-the-pull-request-comment) to find out more.
   </details>
   
   [:umbrella: View full report in Codecov by Harness](https://app.codecov.io/gh/apache/superset/pull/41214?dropdown=coverage&src=pr&el=continue&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache).   
   :loudspeaker: Have feedback on the report? [Share it here](https://about.codecov.io/codecov-pr-comment-feedback/?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache).
   <details><summary> :rocket: New features to boost your workflow: </summary>
   
   - :snowflake: [Test Analytics](https://docs.codecov.com/docs/test-analytics): Detect flaky tests, report on failures, and find test suite problems.
   - :package: [JS Bundle Analysis](https://docs.codecov.com/docs/javascript-bundle-analysis): Save yourself from yourself by tracking and limiting bundle sizes in JS merges.
   </details>


-- 
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: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org


Re: [PR] fix(chart API): apply dashboard filters by live scope, not stale chartsInScope [superset]

Posted by "netlify[bot] (via GitHub)" <gi...@apache.org>.
netlify[bot] commented on PR #41214:
URL: https://github.com/apache/superset/pull/41214#issuecomment-4746837441

   ### <span aria-hidden="true">✅</span> Deploy Preview for *superset-docs-preview* ready!
   
   
   |  Name | Link |
   |:-:|------------------------|
   |<span aria-hidden="true">🔨</span> Latest commit | 494af990e48c0b567820c002a5cb4ffc6e29aa95 |
   |<span aria-hidden="true">🔍</span> Latest deploy log | https://app.netlify.com/projects/superset-docs-preview/deploys/6a34785fc8b6d20008978636 |
   |<span aria-hidden="true">😎</span> Deploy Preview | [https://deploy-preview-41214--superset-docs-preview.netlify.app](https://deploy-preview-41214--superset-docs-preview.netlify.app) |
   |<span aria-hidden="true">📱</span> Preview on mobile | <details><summary> Toggle QR Code... </summary><br /><br />![QR Code](https://app.netlify.com/qr-code/eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJ1cmwiOiJodHRwczovL2RlcGxveS1wcmV2aWV3LTQxMjE0LS1zdXBlcnNldC1kb2NzLXByZXZpZXcubmV0bGlmeS5hcHAifQ.P9ZXvNwzfRzWR73OG92JPYnqHa0d8QZxsC4B7TEJNw4)<br /><br />_Use your smartphone camera to open QR code link._</details> |
   |<span aria-hidden="true">🤖</span> Make changes | [Run an agent on this branch](https://app.netlify.com/projects/superset-docs-preview/agent-runs#HctRCoQgEIDhu8xzslK7Zt2gY4yOomApow9F7N2T3n5--G4onPfSYAUYwDAeNvT28fwQ1mAyMgkfU3Msqs3FidowOWEDcqvxeF-X5ErK10bdKpy-s_55q42iUUqpl1mrScH_AQ) |
   ---
   <!-- [superset-docs-preview Preview](https://deploy-preview-41214--superset-docs-preview.netlify.app) -->
   _To edit notification comments on pull requests, go to your [Netlify project configuration](https://app.netlify.com/projects/superset-docs-preview/configuration/notifications#deploy-notifications)._


-- 
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: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org