pesekon2 opened a new issue, #30059:
URL: https://github.com/apache/superset/issues/30059

   ### Bug description
   
   I provided my `MAPBOX_API_KEY` in `docker/.env` and ran `docker compose` 
using the 4.0.2 `docker-compose-image-tag.yml`. Yet, whenever I open superset 
GUI in the browser and open any of the example map charts (e.g., 
`deck.Polygons`), I can see the polygons but not the Mapbox background. 
   
   The token has been validated through 
<https://api.mapbox.com/tokens/v2?access_token=pk.blabla> with result 
`{"code":"TokenValid","token":{"usage":"pk","user":"pesekon2","authorization":"ckmuxt81k007e2opf8n5gt1fh"}}`
   
   ### How to reproduce the bug
   
   1. Provide MAPBOX_API_KEY
   2. Run `export TAG=4.0.2`
   3. Run `docker compose -f docker-compose-image-tag.yml up`
   4. Get to the charts - open any of the example map (e.g., `deck.Polygons`) 
charts
   
   ### Screenshots/recordings
   
   
![Capture](https://github.com/user-attachments/assets/a2c5bc0a-c997-492b-8941-c565c474a19e)
   
   
   ### Superset version
   
   4.0.2
   
   ### Python version
   
   Not applicable
   
   ### Node version
   
   Not applicable
   
   ### Browser
   
   Firefox
   
   ### 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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to