prisma: Downloading binaries of 4.6.1 fails with wrong sha256 checksum
Bug description
npm ERR! code 1
npm ERR! path /home/d2766cb87e42ac78b6cf6400f1e52be457744eee/node/node_modules/@prisma/engines
npm ERR! command failed
npm ERR! command sh -c -- node scripts/postinstall.js
npm ERR! /home/d2766cb87e42ac78b6cf6400f1e52be457744eee/node/node_modules/@prisma/engines/dist/scripts/postinstall.js:22677
npm ERR! throw new Error(`sha256 of ${url} (zipped) should be ${zippedSha256} but is ${zippedHash}`);
npm ERR! ^
npm ERR!
npm ERR! Error: sha256 of https://binaries.prisma.sh/all_commits/694eea289a8462c80264df36757e4fdc129b1b32/rhel-openssl-1.1.x/migration-engine.gz (zipped) should be b8137868e4dc45f6cb384173fbfc7606b4cb0641328720f2fad95c5e74e6971c but is fbd2f419c17eec8e962e07b8caf71653775c7d8e12db49029b691900513c2354
How to reproduce
$ wget https://binaries.prisma.sh/all_commits/694eea289a8462c80264df36757e4fdc129b1b32/rhel-openssl-1.1.x/migration-engine.gz
--2022-11-11 10:04:38-- https://binaries.prisma.sh/all_commits/694eea289a8462c80264df36757e4fdc129b1b32/rhel-openssl-1.1.x/migration-engine.gz
Resolving binaries.prisma.sh (binaries.prisma.sh)... 13.32.50.55, 13.32.50.41, 13.32.50.7, ...
Connecting to binaries.prisma.sh (binaries.prisma.sh)|13.32.50.55|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 13665486 (13M) [binary/octet-stream]
Saving to: 'migration-engine.gz'
migration-engine.gz 100%[========================================================================================================================================>] 13.03M 30.3KB/s in 1m 46s
2022-11-11 10:06:25 (126 KB/s) - 'migration-engine.gz' saved [13665486/13665486]
$ sha256sum migration-engine.gz
fbd2f419c17eec8e962e07b8caf71653775c7d8e12db49029b691900513c2354 migration-engine.gz
Expected behavior
Correct sha256 checksum when downloading the binary.
Prisma information
Not needed, installation of prisma fails even without a schema.
Environment & setup
OS: CentOS 7.5 Database: MySQL Node.js version: 18.12.1
Prisma Version
4.6.0
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 2
- Comments: 32 (17 by maintainers)
That would be us of course.
I just triggered a minimal invalidation. Can you check if the problem is already resolved maybe?
(The problem here is always that only some CDN nodes are affected, and it seems this time I have no way to reproduce this at all)
Does anyony have a solution?
That’s funny, because we have a demo today but now we cannot rebuild our containers
I thought it depends on prisma version, but it looks like it doesn’t
@janpio Thanks for your help. I installed node_modules successfully after you solve.
@janpio Thanks for the quick help yesterday! 😃
Thanks. Sorry that took so long to connect the dots, only the second time in the last 3 years this happened.
I’ll wait for confirmation from @Trainxy to close the issue, or they can do that themselves.
@janpio Fantastic that worked for me too!
Works for me again! 👍
I was receiving the error message, found this issue and @janpio can confirm that after your comment I was able to run
npm install
without issue.