prisma: `prisma:engine stdout Unknown error`

Recently the prisma:engine logging is full with Unknown error message:

...
  prisma:engine stdout Fetched a connection from the pool +10ms
  prisma:engine stdout Unknown error +23ms
prisma:query BEGIN
  prisma:engine stdout Unknown error +61ms
prisma:query SELECT "public"."BuyerGroup"."id" FROM "public"."BuyerGroup" WHERE 1=1 OFFSET $1
  prisma:engine stdout Unknown error +63ms
prisma:query SELECT "public"."BuyerGroup"."id" FROM "public"."BuyerGroup" WHERE 1=1
  prisma:engine stdout Unknown error +22ms
prisma:query COMMIT
...

Logging can be achieved with DEBUG=* and

const prisma = new PrismaClient({
  log: ['query', 'info', `warn`, `error`],
})

About this issue

Original URL
State: closed
Created 3 years ago
Reactions: 1
Comments: 17 (11 by maintainers)

Most upvoted comments

I tried reproducing and no luck.

The only instance of “Unknown error” in the code, in any of prisma and prisma-engines is imposible it is related to this problem as it a WASM specific code added very recently.

query-engine/driver-adapters/src/wasm/error.rs
11:        .unwrap_or_else(|| "Unknown error".to_string());

The history of commits that added or removed that expression “Unknown error” in both prisma or prisma-engines have been inspected and don’t contain any smoking gun.

I’m going to close this as I can’t reproduce anymore. And it’s uncertain whether this is still an issue.

miguelff on Jan 19, 2024

@tehnorm Which version of prisma and @prisma/client are you using and could you share your Prisma Client query and schema maybe?

along with:

OS: [e.g. Mac OS, Windows, Debian, CentOS, …]
Database: [PostgreSQL, MySQL, MariaDB or SQLite]
Node.js version: [Run node -v to see your Node.js version]

It will help to reproduce this.

Jolg42 on Sep 2, 2021

That would be possible, no recollection after 4 weeks. Will observe if I see it again.

janpio on Jul 28, 2021