You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Across a number of Superset instances, I have noticed that the Mapbox map chart type has an issue where when it is added to a dashboard, the data does not load, until the user interacts with the map by panning or zooming. There do not appear to be any errors in in the browser console or server logs about this. Additionally, none of the Mapbox chart settings (such as Live Render) seem to make a difference.
This issue does not occur when loading a Mapbox map chart in the edit chart view (e.g. in the /explore/... route).
How to reproduce the bug
Add a MapBox map chart.
Add some lat/long data
Notice that the map in Chart Creating / Editing view does always show the data.
Add the MapBox chart to a dashboard.
Load the dashboard.
The chart does not show the data (only the background map of choice is shown).
Interact with the map by panning or zooming.
The data now shows.
Screenshots/recordings
Before I interact with the map:
After I interact with the map:
Superset version
3.0.4
Python version
Not applicable
Node version
Not applicable
Browser
Chrome
Additional context
For the instances where I have seen this issue, they are deployed as an Azure app service using Docker (with the image apache/superset:3.0.3). There are no settings in superset_config.py that should make a difference.
Checklist
I have searched Superset docs and Slack and didn't find a solution to my problem.
I have searched the GitHub issue tracker and didn't find a similar bug report.
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.
The text was updated successfully, but these errors were encountered:
Bug description
Across a number of Superset instances, I have noticed that the Mapbox map chart type has an issue where when it is added to a dashboard, the data does not load, until the user interacts with the map by panning or zooming. There do not appear to be any errors in in the browser console or server logs about this. Additionally, none of the Mapbox chart settings (such as Live Render) seem to make a difference.
This issue does not occur when loading a Mapbox map chart in the edit chart view (e.g. in the
/explore/...
route).How to reproduce the bug
Screenshots/recordings
Before I interact with the map:
![image](https://private-user-images.githubusercontent.com/31662219/316485776-2bb625b0-73ad-46d8-80f9-a0ece02245c0.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjAxMTUzMzUsIm5iZiI6MTcyMDExNTAzNSwicGF0aCI6Ii8zMTY2MjIxOS8zMTY0ODU3NzYtMmJiNjI1YjAtNzNhZC00NmQ4LTgwZjktYTBlY2UwMjI0NWMwLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MDQlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzA0VDE3NDM1NVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPThmNTNkY2YxMTAwNWYzN2NkY2EwMTkwNWI0MmFkOWJlNzY1NmI1NWQwZGFmZTRlMDY5OGI1NzFhZTQzYzFmZjcmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.G6vAVDh3h9ZJbDn6mQgwQy4pRX5n6OXJbZprxuqypVY)
After I interact with the map:
![image](https://private-user-images.githubusercontent.com/31662219/316485893-ec2bcb98-969e-420c-9606-0cc85a300d4d.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjAxMTUzMzUsIm5iZiI6MTcyMDExNTAzNSwicGF0aCI6Ii8zMTY2MjIxOS8zMTY0ODU4OTMtZWMyYmNiOTgtOTY5ZS00MjBjLTk2MDYtMGNjODVhMzAwZDRkLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MDQlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzA0VDE3NDM1NVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTJmY2ZmYWFhZDQxZjE4ZjkzODI5YzEyODcxM2Y2NGQyMDc1NDgwY2M4ZWY1MjEzODI2YTc2YjY2YzVlYmY5MWUmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.4d8YQvQbetNrtDnsy9D3kbIsU556667x9S5thckXuV0)
Superset version
3.0.4
Python version
Not applicable
Node version
Not applicable
Browser
Chrome
Additional context
For the instances where I have seen this issue, they are deployed as an Azure app service using Docker (with the image
apache/superset:3.0.3
). There are no settings insuperset_config.py
that should make a difference.Checklist
The text was updated successfully, but these errors were encountered: