-
Notifications
You must be signed in to change notification settings - Fork 3k
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
[cuda] [npm/nodejs] Failed to download the binaries: 404 Not Found #22877
Comments
after looking at the code |
Which docs specifically? |
https://github.com/microsoft/onnxruntime/blob/main/js/node/README.md which gets pulled into the readme over at: https://www.npmjs.com/package/onnxruntime-node see the bottom note that mentions v12 (which is non existent now) |
@fs-eire should we update the install script if we're not producing CUDA 11 and 12 packages to remove the option to choose? |
Background: There is a max size limit for NPM package, so it is impossible to include CUDA binaries inside Before 1.18.x, there are both onnxruntime-win-x64-gpu-1.18.0.zip and onnxruntime-win-x64-gpu-cuda12-1.18.0.zip in the github release assets, containing the CUDA v11 bits and CUDA v12 bits.
Since 1.19.x, CUDA v12 became default and the I can make a change in the installation script to fix it for CUDA v12. However, it may be difficult for CUDA v11 since there is no public assets. |
I will make a change to fix the installation script for cuda v12. |
…oft#22984) ### Description This PR updates installation script to fix it for CUDA v12. However, it may be difficult for CUDA v11 since the steps are quite complicated to automate. Added a few lines of instructions instead. fixes microsoft#22877
…oft#22984) ### Description This PR updates installation script to fix it for CUDA v12. However, it may be difficult for CUDA v11 since the steps are quite complicated to automate. Added a few lines of instructions instead. fixes microsoft#22877
the readme tells you to use
to pull in the cuda binaries for linux x64; it tries to download:
which indeed does not exist, what does exist is:
but there is no way to pass an empty string to
--onnxruntime-node-install
so that it assembles the right URL.The text was updated successfully, but these errors were encountered: