```/home/tharshan/Projects/uservitals/node_modules...
# orm-help
t
Copy code
/home/tharshan/Projects/uservitals/node_modules/@prisma/client/runtime/index.js:34784
          throw new import_engine_core.PrismaClientUnknownRequestError(message, this.prisma._clientVersion);
                ^

PrismaClientUnknownRequestError2 [PrismaClientUnknownRequestError]: 
Invalid `prisma.user.findUnique()` invocation:


  Can't perform request, as the Engine has already been stopped
    at cb (/home/tharshan/Projects/uservitals/node_modules/@prisma/client/runtime/index.js:34784:17)
    at processTicksAndRejections (node:internal/process/task_queues:94:5)
    at async searchContact (/home/tharshan/Projects/uservitals/api/db/seed.js:54:18)
    at async /home/tharshan/Projects/uservitals/api/db/seed.js:840:23 {
  clientVersion: '2.21.2'
}
j
You running this from 'db/seed.js'?
can you share that file?
t
Correct
We some sensitive data in there
Is there anything specific you are looking for?
j
ah okay
maybe the
main()
-like function or the line where findUnique is being called?
t
So we found the error is inconsistent. It can be that error, or another one on each run
We found that it works well on node 14
but this is happening on node 15
j
humm, sorry not sure there
j
The error means that the Query Engine, which is running in the background, crashed more or less.
Usually you should have an error earlier than that.
Maybe with
DEBUG=*
set you can understand better what is happening.
Definitely worth an issue on GitHub.
t
Oh I did not know about that!
@janpio I am unclear if we are doing something wrong or it's prisma
Can I DM you the seed.js and output with debug?
You can let me know if we should file an issue
j
Yep sure.
Our best way forward would be to have an issue with all the ifnromation so we can reproduce.
But let me take a look first and I can see if anything pops out.