You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "ruslan-murzag (via GitHub)" <gi...@apache.org> on 2024/10/31 06:47:31 UTC
[I] Images Not Displaying Due to Content Security Policy (CSP) Restrictions [superset]
ruslan-murzag opened a new issue, #30761:
URL: https://github.com/apache/superset/issues/30761
### Bug description
Images hosted on external URLs are not displaying in Apache Superset due to Content Security Policy (CSP) restrictions. Despite configuring TALISMAN_CONFIG to allow all sources, the browser console still reports CSP violations, specifically blocking image loading from external URLs.
**Steps to Reproduce:**
1. Configure TALISMAN_CONFIG in superset_config.py with settings to allow all sources:
```
TALISMAN_CONFIG = {
"content_security_policy": {
"default-src": ['*'],
"img-src": ['*'],
"worker-src": ['*'],
"connect-src": ['*'],
"object-src": ['*'],
"style-src": ['*'],
"script-src": ['*'],
},
"force_https": False,
"session_cookie_secure": False,
}
```
2. Attempt to display an image from an external URL in Superset.
The image should display as configured, following the img-src: '*' directive.
**Actual Behavior:**
The image does not load, and the browser console shows a CSP error similar to the following:
```
Refused to load the image 'http://101.30.83.81:9000/images-superset/photo_2024-10-29_13-57-16.jpg' because it violates the following Content Security Policy directive: "img-src 'self' blob: data: https://apachesuperset.gateway.scarf.sh https://static.scarf.sh/".
```
**Impact:**
This CSP restriction prevents images hosted on external URLs from being displayed in Superset, limiting the ability to include necessary external visual content.
**Request:**
An option to fully relax or disable CSP checks specifically for images would provide flexibility, ensuring that Superset can display images hosted on external URLs as intended.
**Additional Context:**
This issue specifically affects the display of externally hosted images within Superset, which are essential for various dashboards and visualizations.
### Screenshots/recordings
### Superset version
4.0.2
### Python version
3.9
### Node version
16
### Browser
Chrome
### Additional context
_No response_
### 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: notifications-unsubscribe@superset.apache.org.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: [I] Images Not Displaying Due to Content Security Policy (CSP) Restrictions [superset]
Posted by "ruslan-murzag (via GitHub)" <gi...@apache.org>.
ruslan-murzag commented on issue #30761:
URL: https://github.com/apache/superset/issues/30761#issuecomment-2464357595
Hello @mistercrunch @rusackas, I found a solution, though it seems unusual. To display images, I need to modify two configurations:
- TALISMAN_CONFIG
- TALISMAN_DEV_CONFIG
However, I’m running docker-compose-image-tag.yml, which indicates a production setup, not a development one.
--
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: [I] Images Not Displaying Due to Content Security Policy (CSP) Restrictions [superset]
Posted by "mistercrunch (via GitHub)" <gi...@apache.org>.
mistercrunch commented on issue #30761:
URL: https://github.com/apache/superset/issues/30761#issuecomment-2465760730
All of our `docker compose` setups, including docker-compose-image-tag.yml, are NOT recommended for production use.
From https://superset.apache.org/docs/installation/docker-compose/
<img width="1019" alt="Screenshot 2024-11-08 at 1 11 01 PM" src="https://github.com/user-attachments/assets/1bc13819-4cbf-47f9-a5ef-5f24204a66b0">
On top of what is described there, there was a challenge around segmentation while supporting dev AND prod use cases within docker-compose semantics, where there was a lot of conditionality in docker-compose (if dev then do_this else do_something_else) which could lead to confusion and security issues. Because of that we decided to recommend helm/k8s/minikube for prod use cases, where we can make sure all the conditions and configurations point to prod/secure images and configurations.
--
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: [I] Images Not Displaying Due to Content Security Policy (CSP) Restrictions [superset]
Posted by "varun-verma-code (via GitHub)" <gi...@apache.org>.
varun-verma-code commented on issue #30761:
URL: https://github.com/apache/superset/issues/30761#issuecomment-2722994068
https://github.com/apache/superset/issues/30761#issuecomment-2464357595
@ruslan-murzag I have added the config to both places, however, I still see the same issue. Here's my config:
`TALISMAN_CONFIG = {
"content_security_policy": {
"default-src": ["'self'"],
"img-src": ["'self'", "data:","blob:"],
"worker-src": ["'self'", "blob:"],
"connect-src": [
"'self'",
"https://api.mapbox.com",
"https://events.mapbox.com",
],
"object-src": "'none'",
"style-src": ["'self'", "'unsafe-inline'"],
"script-src": ["'self'", "'strict-dynamic'"],
},
"content_security_policy_nonce_in": ["script-src"],
"force_https": False,
}
# React requires `eval` to work correctly in dev mode
TALISMAN_DEV_CONFIG = {
"content_security_policy": {
"default-src": ["'self'"],
"img-src": ["'self'", "data:","blob:"],
"worker-src": ["'self'", "blob:"],
"connect-src": [
"'self'",
"https://api.mapbox.com",
"https://events.mapbox.com",
],
"object-src": "'none'",
"style-src": ["'self'", "'unsafe-inline'"],
"script-src": ["'self'", "'unsafe-inline'", "'unsafe-eval'"],
},
"content_security_policy_nonce_in": ["script-src"],
"force_https": False,
}`
Am I missing anything?
--
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: [I] Images Not Displaying Due to Content Security Policy (CSP) Restrictions [superset]
Posted by "rusackas (via GitHub)" <gi...@apache.org>.
rusackas commented on issue #30761:
URL: https://github.com/apache/superset/issues/30761#issuecomment-2455964532
Does it work without brackets, e.g. `'img-src': '*',`?
--
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: [I] Images Not Displaying Due to Content Security Policy (CSP) Restrictions [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
dosubot[bot] commented on issue #30761:
URL: https://github.com/apache/superset/issues/30761#issuecomment-2449147638
<!-- Answer -->
A similar issue was discussed in a closed thread titled [Cached thumbnails not showing in browser due to CSP](https://github.com/apache/superset/issues/25698). The solution involved modifying the `img-src` directive in the Content Security Policy to include `blob:`, making it `"img-src": ["'self'", "data:", "blob:"]`. This change allowed cached thumbnails to display correctly. Additionally, this issue was addressed in version 3.0.1 of Superset <sup>[[1]](https://github.com/apache/superset/issues/25698)</sup>.
In your case, it seems that despite setting `img-src` to `'*'`, the CSP is still enforcing restrictions. This might be due to a misconfiguration or an override elsewhere in the application. It's generally not recommended to use `'*'` for CSP directives due to security risks, as it allows content from any source, which can expose your application to vulnerabilities like XSS attacks <sup>[[2]](https://github.com/apache/superset/blob/master/docs/docs/security/security.mdx)</sup>.
To troubleshoot, ensure that there are no other configurations or middleware that might be overriding your CSP settings. Additionally, consider specifying trusted domains explicitly in the `img-src` directive instead of using `'*'` to maintain security while allowing necessary external images.
<!-- Dosu Comment Footer -->
*To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
--
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: [I] Images Not Displaying Due to Content Security Policy (CSP) Restrictions [superset]
Posted by "ruslan-murzag (via GitHub)" <gi...@apache.org>.
ruslan-murzag commented on issue #30761:
URL: https://github.com/apache/superset/issues/30761#issuecomment-2452735008
@mistercrunch I considered that and ran the `flask CLI` in the worker container to retrieve the `TALISMAN_CONFIG` variable. Here’s the code I used:
```python
from flask import current_app
print(current_app.config.get("TALISMAN_CONFIG"))
```
This returned the same configuration I had defined in the config file. Is this an appropriate way to verify the TALISMAN_CONFIG, or would you recommend a different method?
--
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: [I] Images Not Displaying Due to Content Security Policy (CSP) Restrictions [superset]
Posted by "mistercrunch (via GitHub)" <gi...@apache.org>.
mistercrunch commented on issue #30761:
URL: https://github.com/apache/superset/issues/30761#issuecomment-2455680490
Seems like a fair way to validate the configuration. In that context, do you still get the `scarf.sh`-related log/error messages? Where could that be coming from if you `TALISMAN_CONFIG` is not referencing it? A zombie/competing process?
There's a lot of different ways to confirm or double check that the endpoint you are hitting is aligned with the configuration / process you think you are running. Do you still get an error/warning after killing all processes (trying to ensure it's not a zombie or other process) or just no answer as expected? Could you add or alter an exsiting endpoint to serve the `app.config.get("TALISMAN_CONFIG")`?
--
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: [I] Images Not Displaying Due to Content Security Policy (CSP) Restrictions [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
dosubot[bot] commented on issue #30761:
URL: https://github.com/apache/superset/issues/30761#issuecomment-2723024586
<!-- Answer -->
Given the specific configuration and the error message, here are some targeted points to consider:
1. **Configuration Consistency**: Ensure that both `TALISMAN_CONFIG` and `TALISMAN_DEV_CONFIG` are consistent and correctly set. Since the error message shows `img-src 'self' data:`, it seems like the `blob:` directive is missing. Double-check that the configuration files are correctly loaded and that there are no typos or syntax errors.
2. **Environment Mode**: Verify that the application is not inadvertently using `TALISMAN_DEV_CONFIG` due to being in debug mode. This can happen if the `DEBUG` flag is set to `True` or if the application is running in a debug environment. Ensure that the application is running in the intended mode by checking the `DEBUG` setting and the environment variables <sup>[[1]](https://github.com/apache/superset/blob/master/superset/initialization/__init__.py)</sup>.
3. **Middleware or Overrides**: Investigate if there is any middleware or additional configuration that might override the CSP settings. This could include other Flask extensions or server configurations that might be setting CSP headers independently <sup>[[1]](https://github.com/apache/superset/blob/master/superset/initialization/__init__.py)</sup>.
4. **Docker and Environment Variables**: If using Docker, ensure that the environment variables are correctly set and that the container is using the intended configuration. Sometimes, Docker-specific settings or environment variables can lead to unexpected behavior.
5. **Inspect HTTP Headers**: Use browser developer tools or a tool like `curl` to inspect the HTTP headers being sent by the server. This can help confirm whether the CSP headers are being set as expected and identify any discrepancies.
By focusing on these areas, you can pinpoint where the configuration might be going wrong and ensure that the correct CSP settings are applied.
<!-- Dosu Comment Footer -->
*To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
---
<sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/6790aff8-733f-41f3-8aa5-1b3dda12e5b8?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/6790aff8-733f-41f3-8aa5-1b3dda12e5b8?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/6790aff8-733f-41f3-8aa5-1b3dda12e5b8?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/6790aff8-733f-41f3-8aa5-1b3dda12e5b8?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/6790aff8-733f-41f3-8aa5-1b3dda12e5b8?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/6790aff8-733f-41f3-8aa5-1b3dda12e5b8?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/6790aff8-733f-41f3-8aa5-1b3dda12e5b8?feedback_type=other)</sup>
--
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: [I] Images Not Displaying Due to Content Security Policy (CSP) Restrictions [superset]
Posted by "Ananda2k22 (via GitHub)" <gi...@apache.org>.
Ananda2k22 commented on issue #30761:
URL: https://github.com/apache/superset/issues/30761#issuecomment-2531113446
After updating the content security policy still getting the error
"img-src": ["'self'", "data:", "blob:"] used this
--
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: [I] Images Not Displaying Due to Content Security Policy (CSP) Restrictions [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
dosubot[bot] commented on issue #30761:
URL: https://github.com/apache/superset/issues/30761#issuecomment-2723020602
<!-- Answer -->
To troubleshoot the issue with the Content Security Policy (CSP) not reflecting the expected configuration, here are a few steps to consider:
1. **Verify Configuration Loading**: Ensure that the `superset_config.py` file is correctly placed and loaded by the Superset application. You can confirm this by checking the logs for any messages indicating the configuration file being loaded or by printing the configuration at runtime, as you have done.
2. **Check for Overrides**: There might be other configurations or middleware that override the CSP settings. Double-check any other configuration files or environment variables that might affect the CSP.
3. **Environment and Debug Mode**: Ensure that the application is not inadvertently running in a development mode, which might cause `TALISMAN_DEV_CONFIG` to be used instead of `TALISMAN_CONFIG`. This can happen if the `DEBUG` flag is set to `True` or if the application is running in a debug environment <sup>[[1]](https://github.com/apache/superset/blob/master/superset/initialization/__init__.py)</sup>.
4. **Docker Environment**: If you are using Docker, ensure that the correct environment variables are set and that the container is using the intended configuration. Sometimes, environment variables or Docker-specific settings can lead to unexpected behavior.
5. **Restart the Application**: After making changes to the configuration, ensure that the Superset application is fully restarted to apply the new settings.
6. **Inspect HTTP Headers**: Use browser developer tools or a tool like `curl` to inspect the HTTP headers being sent by the server. This can help confirm whether the CSP headers are being set as expected.
7. **Check for Cached Responses**: Sometimes, browsers cache CSP headers. Clear the browser cache or try accessing the application in an incognito window to ensure you're seeing the latest headers.
By following these steps, you should be able to identify where the configuration might be going wrong and ensure that the correct CSP settings are applied.
<!-- Dosu Comment Footer -->
*To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
---
<sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/211fafc9-07ad-4574-bf34-fddd05bb5a7c?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/211fafc9-07ad-4574-bf34-fddd05bb5a7c?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/211fafc9-07ad-4574-bf34-fddd05bb5a7c?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/211fafc9-07ad-4574-bf34-fddd05bb5a7c?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/211fafc9-07ad-4574-bf34-fddd05bb5a7c?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/211fafc9-07ad-4574-bf34-fddd05bb5a7c?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/211fafc9-07ad-4574-bf34-fddd05bb5a7c?feedback_type=other)</sup>
--
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: [I] Images Not Displaying Due to Content Security Policy (CSP) Restrictions [superset]
Posted by "mistercrunch (via GitHub)" <gi...@apache.org>.
mistercrunch commented on issue #30761:
URL: https://github.com/apache/superset/issues/30761#issuecomment-2723022709
@dosubot your answer is pretty generic, now based on his earlier comment and SPECIFIC configuration, can you identify what exactly could be wrong with his configuration given the error message he's getting?
--
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: [I] Images Not Displaying Due to Content Security Policy (CSP) Restrictions [superset]
Posted by "mistercrunch (via GitHub)" <gi...@apache.org>.
mistercrunch commented on issue #30761:
URL: https://github.com/apache/superset/issues/30761#issuecomment-2452326494
The fact that you have a log explicitly stating `Refused to load the image 'http://101.30.83.81:9000/images-superset/photo_2024-10-29_13-57-16.jpg' because it violates the following Content Security Policy directive: "img-src 'self' blob: data: https://apachesuperset.gateway.scarf.sh https://static.scarf.sh/".` seems to be pointing to the default `config.TALISMAN_CONFIG` being in effect (or maybe not the default config, but one that references scarf.sh) and doesn't match the shared `TALISMAN_CONFIG` that you think should be in effect.
If would suggest double checking that your config file is properly found and loaded.
--
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: [I] Images Not Displaying Due to Content Security Policy (CSP) Restrictions [superset]
Posted by "ruslan-murzag (via GitHub)" <gi...@apache.org>.
ruslan-murzag closed issue #30761: Images Not Displaying Due to Content Security Policy (CSP) Restrictions
URL: https://github.com/apache/superset/issues/30761
--
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: [I] Images Not Displaying Due to Content Security Policy (CSP) Restrictions [superset]
Posted by "ruslan-murzag (via GitHub)" <gi...@apache.org>.
ruslan-murzag commented on issue #30761:
URL: https://github.com/apache/superset/issues/30761#issuecomment-2465814224
@mistercrunch ok i got 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: [I] Images Not Displaying Due to Content Security Policy (CSP) Restrictions [superset]
Posted by "mistercrunch (via GitHub)" <gi...@apache.org>.
mistercrunch commented on issue #30761:
URL: https://github.com/apache/superset/issues/30761#issuecomment-2723017772
@dosubot can you help troubleshoot @varun-verma-code's configuration?
--
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