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

   A clear and concise description of what the bug is.
   
   #### How to reproduce the bug
   
   1. Deploy superset helm chart 0.10.14 (currently successfully deployed 
version = 0.10.9)
   
   ### Expected results
   
   Superset deploys to Kubernetes cluster successfully.
   
   ### Actual results
   
   apache-superset-init-db fails to pip install cryptography with this error 
message:
   
   ```
   ERROR: pip's dependency resolver does not currently take into account all 
the packages that are installed. This behaviour is the source of the following 
dependency conflicts.apache-superset 3.0.1 requires cryptography<40,>=39.0.1, 
but you have cryptography 41.0.5 which is incompatible.
   ```
   
   #### Screenshots
   
   N/A
   
   
   ### Environment
   
   (please complete the following information):
   
   - browser type and version: N/A
   - superset version: `3.0.1 (Helm Chart 0.10.14)`
   - python version: `defined in Helm Chart`
   - node.js version: `defined in Helm Chart`
   - any feature flags active: `none`
   
   ### Checklist
   
   Make sure to follow these steps before submitting your issue - thank you!
   
   - [x] I have checked the superset logs for python stacktraces and included 
it here as text if there are any.
   - [x] I have reproduced the issue with at least the latest released version 
of superset.
   - [x] I have checked the issue tracker for the same issue and I haven't 
found one similar.
   
   ### Additional context
   
   We are deploying with ArgoCD.
   


-- 
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