prisma: 5.5.0/1: `Error: sha256 checksum of https://binaries.prisma.sh/all_commits/475c616176945d72f4330c92801f0c5e6398dc0f/windows/query_en gine.dll.node.gz (zipped) should be 748d039badd0919d022fff7d554b66b6937b79035861a6ae9a80c5a95eee76f5 but is b867ad335ee6f58c6a38f665dd641c95e6adff3061f92b7613c62cae1c3362bb`
Bug description
Trying to use command npx prisma init --datasource-provider sqlite but i get an Error:
sha256 checksum of https://binaries.prisma.sh/all_commits/475c616176945d72f4330c92801f0c5e6398dc0f/windows/query_engine.dll.node.gz (zipped) should be 748d039badd0919d022fff7d554b66b6937b79035861a6ae9a80c5a95eee76f5 but is b867ad335ee6f58c6a38f665dd641c95e6adff3061f92b7613c62cae1c3362bb
How to reproduce
Expected behavior
No response
Prisma information
// Add your schema.prisma
// Add your code using Prisma Client
Environment & setup
- OS: Windows10
- Database: SQLite
- Node.js version: 20.9.0
Prisma Version
5.5.1
About this issue
- Original URL
- State: closed
- Created 8 months ago
- Reactions: 8
- Comments: 26 (8 by maintainers)
Thanks everyone, we understood the problem and are working on a fix. Will post here. Until then please keep using an older version that works for you.
Background: 5.5.1 shipped with the same engine version as 5.5.0, and because of a bug that uploaded the same engine version again - but from a different build with different checksums. If you installed 5.5.0 before, you already have the engine file and because of how the checksum flow works, it will compare the new checksum to the old engine file - and you get the message above. That is not supposed to happen.
We are currently doing 2 things:
Thanks everyone, we now also released a fresh version 5.5.2 with a new engine version, that should completely avoid these problems altogether - just to be safe.
If anyone is still having any problems, please let us know asap.
It`s all good now. Thank you!
v 5.4.2 works for me also ✔ Generated Prisma Client (v5.4.2) to .\node_modules@prisma\client in 166ms
The incident should now be resolved for most of you.
Try this first
npx prisma -vfor example, or any other CLI commandThat succeeded? Let us know that only retrying helped, we’ll be happy to hear from you. If that doesn’t succeed, you’ll need to reset the downloaded engines cache that Prisma maintains on your local computer.
Instructions for deleting the cache
Linux/macOS
~/.cache/prisma/master/, you can run the following commandrm -r ~/.cache/prisma/master/Windows
node_modulesdirectoryecho %APPDATA%or if using Powershellecho $Env:APPDATAPrismasubdirectory if it existsmastersubdirectoryLast step
npx prisma -vfor example, or any other CLI commandThat succeeded? Let us know that deleting the cache helped, we’ll be happy to hear from you.
@GennadyKhalilov @gkilmain @markmark21 To confirm, you are all trying to install 5.5.1?
I’m getting similar message on mac m1 when i run
npx prisma initDownloading Prisma engines for Node-API for darwin-arm64 [========== ] 48%Error: sha256 checksum of https://binaries.prisma.sh/all_commits/475c616176945d72f4330c92801f0c5e6398dc0f/darwin-arm64/schema-engine.gz (zipped) should be d30addaa7ce73515d633e3e5ae7a9636ed69a31fee5cd636dc2e6d242a923560 but is 3e9198dfc6d5e1fb8de3cf8ae336fc75004996eac87469bb75ef463aaafb7748I’ve tried clearing my cache
rm -rf ~/.prismabut that didn’t help. I’m on node 18.18@janpio Not happening now. I may have rolled back incorrectly with pnpm.
I have similar issue with Prisma 5.5.0 on linux(fedora 38) with this command :
pnpm dlx prisma migrate dev. Error:Temporary solution is use Prisma 5.0.1 :
pnpm dlx prisma@5.3.1 migrate dev.On version 5.5.0 the same error
I’m having similar issue with Prisma 5.5.1 (quite sure it was with 5.5.0 too) but with this line instead in a Docker container build (on
node:20.8.1-alpine3.18):Building with Prisma 5.4.2 works (in my case at least). Then, going in the container and updating Prisma to 5.5.1, and running
node_modules/.bin/prisma generatetries to download the file and gives the identical error message.I installed 5.2 and problem got fixed
temporaryly changing it to version 5.2 solved my issue,