Hi we have started getting this error on Prisma cl...
# orm-help
n
Hi we have started getting this error on Prisma cloud
Copy code
Error starting Prisma Client: {
  "message": "Could not find query-engine binary. Searched in /var/task/node_modules/@prisma/sdk/query-engine-rhel-openssl-1.0.x and /var/task/node_modules/@prisma/query-engine-rhel-openssl-1.0.x",
  "stack": "Error: Could not find query-engine binary. Searched in /var/task/node_modules/@prisma/sdk/query-engine-rhel-openssl-1.0.x and /var/task/node_modules/@prisma/query-engine-rhel-openssl-1.0.x\n    at resolveBinary (/var/task/node_modules/@prisma/sdk/dist/resolveBinary.js:93:9)\n    at async getConfigBinary (/var/task/node_modules/@prisma/sdk/dist/engine-commands/getConfig.js:102:27)\n    at async getConfig (/var/task/node_modules/@prisma/sdk/dist/engine-commands/getConfig.js:54:12)\n    at async Object.getGenerators (/var/task/node_modules/@prisma/sdk/dist/getGenerators.js:93:18)\n    at async Object.getGenerator (/var/task/node_modules/@prisma/studio-pcw/dist/generators.js:13:30)\n    at async PCW.getDMMF (/var/task/node_modules/@prisma/studio-pcw/dist/pcw.js:56:47)\n    at async handler (/var/task/.next/server/pages/api/databrowser.js:703:17)\n    at async apiResolver (/var/task/node_modules/next/dist/next-server/server/api-utils.js:8:1)\n    at async Server.handleApiRequest (/var/task/node_modules/next/dist/next-server/server/next-server.js:67:462)\n    at async Object.fn (/var/task/node_modules/next/dist/next-server/server/next-server.js:59:492)"
}
Error: Error starting Prisma Client: {
  "message": "Could not find query-engine binary. Searched in /var/task/node_modules/@prisma/sdk/query-engine-rhel-openssl-1.0.x and /var/task/node_modules/@prisma/query-engine-rhel-openssl-1.0.x",
  "stack": "Error: Could not find query-engine binary. Searched in /var/task/node_modules/@prisma/sdk/query-engine-rhel-openssl-1.0.x and /var/task/node_modules/@prisma/query-engine-rhel-openssl-1.0.x\n    at resolveBinary (/var/task/node_modules/@prisma/sdk/dist/resolveBinary.js:93:9)\n    at async getConfigBinary (/var/task/node_modules/@prisma/sdk/dist/engine-commands/getConfig.js:102:27)\n    at async getConfig (/var/task/node_modules/@prisma/sdk/dist/engine-commands/getConfig.js:54:12)\n    at async Object.getGenerators (/var/task/node_modules/@prisma/sdk/dist/getGenerators.js:93:18)\n    at async Object.getGenerator (/var/task/node_modules/@prisma/studio-pcw/dist/generators.js:13:30)\n    at async PCW.getDMMF (/var/task/node_modules/@prisma/studio-pcw/dist/pcw.js:56:47)\n    at async handler (/var/task/.next/server/pages/api/databrowser.js:703:17)\n    at async apiResolver (/var/task/node_modules/next/dist/next-server/server/api-utils.js:8:1)\n    at async Server.handleApiRequest (/var/task/node_modules/next/dist/next-server/server/next-server.js:67:462)\n    at async Object.fn (/var/task/node_modules/next/dist/next-server/server/next-server.js:59:492)"
}
    at ki.init (<https://cloud.prisma.io/studio/assets/index.js:1:104126>)
(cc @siddhant @janpio)
👋 1
j
Anything special in your schema file? (Especially in the generator section)
n
it runs in normal Prisma studio fine locally, so I feel like its to do with cloud version
not sure what to check for in terms of generator/schema
Copy code
generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["orderByRelation", "referentialActions", "nApi"]
}
j
Can you remove
nApi
from your schema and try again? The error message is kinda related to that, so maybe that helps.
👍 1
I take that back, this is also broken on other projects.
Thanks for the report, we will investigate and probably roll back a recent change.
🙌 1
This should work again now.
Can you please confirm?
n
@janpio all good now, thank you
j
Thanks for the report. We will figure out what went wrong with that depoyment, and most importantly why it was not detected by our tests before and after deployment.
🙌 1