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

   ### Bug description
   
   The 5.0,0-dev found on https://hub.docker.com/r/apache/superset does not 
contain geckodriver.
   Previous versions (e.g. 4.1.2-dev) did include these.
   
   This breaks alerts and reports.
   
   Steps to reproduce:
   1. Pull image: `docker pull apache/superset:5.0.0-dev`
   2. Create and enter bash shell in container: ` docker run -it --rm 
apache/superset:5.0.0-dev bash`
   3. `which geckodriver` should output a valid path to geckodriver (like 
`/usr/local/bin/geckodriver`), but it does not.
   
   ### Screenshots/recordings
   
   
![Image](https://github.com/user-attachments/assets/12176bbc-dea6-4ded-b6b0-fc2c3107159c)
   
   ### Superset version
   
   5.0.0
   
   ### Python version
   
   Not applicable
   
   ### Node version
   
   Not applicable
   
   ### Browser
   
   Firefox
   
   ### Additional context
   
   I did not find any information in the docs/slack/issues page that this would 
be removed.
   
   I'll check the github workflows some more. It might have to do with 
releasing both v5.0.0 and 5.0.0 (first one was by mistake I think).
   
   ### 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