Skip to content
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

compilation fails on arm64 architecture when installing npm dependencies #523

Open
andresrcs opened this issue Apr 26, 2022 · 1 comment

Comments

@andresrcs
Copy link

When trying to compile the latest version of shiny-server (v1.5.18.987) on arm64 architecture (Raspberry Pi) the installation of npm modules fails because the checksum of rstudio/node-optimist doesn't match

~/shiny-server/tmp $ (cd .. && ./bin/npm  install)
npm WARN tarball tarball data for optimist@git+ssh://git@github.com/rstudio/node-optimist.git#dbbadda31e53b63225a57e172a528b1ddc52be52 (sha512-3RAVyfbptsR6HOFA0BFNLyw8ZXXDRWf5P3tIslbNt12kTikaRWepRR9vLHMyibIZeNfScI9uGqcn1KfbIAeuXA==) seems to be corrupted. Trying again.
npm WARN tarball tarball data for optimist@git+ssh://git@github.com/rstudio/node-optimist.git#dbbadda31e53b63225a57e172a528b1ddc52be52 (sha512-3RAVyfbptsR6HOFA0BFNLyw8ZXXDRWf5P3tIslbNt12kTikaRWepRR9vLHMyibIZeNfScI9uGqcn1KfbIAeuXA==) seems to be corrupted. Trying again.
npm ERR! code EINTEGRITY
npm ERR! sha512-3RAVyfbptsR6HOFA0BFNLyw8ZXXDRWf5P3tIslbNt12kTikaRWepRR9vLHMyibIZeNfScI9uGqcn1KfbIAeuXA== integrity checksum failed when using sha512: wanted sha512-3RAVyfbptsR6HOFA0BFNLyw8ZXXDRWf5P3tIslbNt12kTikaRWepRR9vLHMyibIZeNfScI9uGqcn1KfbIAeuXA== but got sha512-ZwrJM2WaOJesJGZlejLqAiBAE6Ts2PZNk1pQ/x1uTMsQw83BaXWShjqCbhh5bPQUNrlx2Ijz1dOr0hLmlkxKag==. (12281 bytes)

This doesn't happen on x64 architecture, I know you do not support arm64 architecture but I would be really grateful if you could give me a clue on what could be going wrong. Compilation used to work smoothly with all previous versions of shiny-server on arm64 (I currently have v1.5.17.973 installed) so I have no idea what could be going wrong

@elgarteo
Copy link

elgarteo commented May 3, 2022

I ran into the same problem when compiling it on Raspberry Pi as well. Updating the integrity for node_modules/optimist in npm-shrinkwrap.json did the trick.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants