-
Notifications
You must be signed in to change notification settings - Fork 12.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Installing error #28374
Comments
To address the installation errors and deprecated dependency warnings you're encountering with Superset, let's tackle the issues step by step.
By following these steps, you should be able to address the installation errors and deprecated dependency warnings. If you encounter further issues, providing more detailed error messages will be crucial for further assistance.
|
Upgrading npm and node will likely be part of Superset 5.0. We just upgraded it, so we're letting that soak before we do it again. I think core-js is a subdependency of other modules... hopefully it'll fade over time. Feel free to open some dependency bumps and/or help some dependabot PRs to become mergable, that'll all help move this effort forward. |
@dosu ,
C:\Harsh\Projects\New folder\superset>npm update core-js
failed to solve: process "/bin/sh -c npm ci" did not complete successfully: exit code: 1 |
To address the Docker build and network issues you're encountering with Superset on Windows, here are some tailored steps to help resolve these problems:
By following these steps, you should be able to mitigate the build and network issues you're facing with Superset on Docker. If you continue to experience problems, providing detailed error messages and logs can help further diagnose and resolve the issues.
|
HarshPrajapati2309 facing same issue , were you able to find a way around it ? |
If you're encountering similar Docker build and network issues as described, following the steps outlined previously can help resolve these problems. Specifically, switching to WSL2 for Docker on Windows, ensuring Docker Desktop is correctly configured, updating all dependencies, and following the official setup instructions for Docker Compose are crucial steps. Additionally, regularly updating Docker images with
|
Install Ubuntu from Microsoft store , Enable developer mode in windows , Enable Windows for Linux and open ubuntu , and run this commands , one by one: sudo apt update |
Getting this error as well. Seems Docker images are unbuildable using
Had to build dev version in local environment by myself. |
I am also getting the error while setting up - docker
I am in did anyone able resolve this |
I ran into this recently as well, and @mistercrunch suggest throwing more memory at Docker. That indeed seems to have solved the immediate issue, but doesn't really explain why it recently stopped working with Docker's default memory settings. |
We should publish docker recommended settings though it's a bit of a moving target. Also thinning the images could go a long way. That lean image is pretty lean, but that dev one is a bit bloated. |
I finally got it to work with giving Docker more memory as well. It used 16.31 GB at its peak for me |
Yeah it's brutal - worst step is |
This can help a bit: #28784 |
Bug description
The npm warnings indicate deprecated dependencies and suggest upgrading to newer versions. Specifically, core-js@2.6.12 is flagged as no longer maintained and not recommended due to potential performance issues. Additionally, there's a notice about updating npm itself to version 10.7.0.
How to reproduce the bug
How to Reproduce the Bug:
Navigate to the specific location or perform the specified action.
Screenshots/recordings
Superset version
master / latest-dev
Python version
3.9
Node version
16
Browser
Chrome
Additional context
/bin/sh -c npm run ${BUILD_CMD}" did not complete successfully: exit code: 1
Checklist
The text was updated successfully, but these errors were encountered: