Hi all, I've been regularly having a local error f...
# prisma-client
t
Hi all, I've been regularly having a local error for some time now.
Copy code
Error:
Invalid `prisma.project.findMany()` invocation in
webpack-internal:///./packages/prisma/repository/Project.ts:41:84

  Unknown error in Prisma Client

This is a non-recoverable error which probably happens when the Prisma Query Engine has a panic.
I don't get it because the query only works every other time. How if the server was overloaded or something... I use NextJS and Prisma (both are up to date in terms of versions) with Postgres in database Do you have a lead or an idea ? Do we need to set up a pgBouncer?
j
The error does not indicate that there is anything wrong with the connection.
Do you have any additional output?
Tried setting
DEBUG=*
to see what is going on under the hood?
Is this reproducible consistently (althouhg only 50%)?
t
I’ve got the star debug, but the rest is unreadable. Nothing relevant, I feel like
message has been deleted
j
Ha that is actually a link! Can you click it?
It should open a prefilled GH issue form with some relevant information.
t
Yeah, it’s getting more and more recurring. In fact, the bigger the application gets, the more it gets stuck. I even have a “native” query (executeRaw) which is completely blocked and yet it works fine if I run it by hand.
j
The newest release 2.1.3 that happened this morning also improved that link a lot - so if you are not on that version yet maybe try to upgrade.
t
Oh no, I haven’t seen the release, I’m doing this right now to see.
prisma rainbow 1
j
If it doesn't help, just copy/pasting the link here might also be an option for me to get some information.
t
Ok I have more info I feel like 🙂
message has been deleted
j
@tim2, who is just speaking in #prismaday will like that 😄 he fixed that this morning.
😄 1
that output looks pretty normal though
nothing bad in there
t
I have the impression that this is related to the configuration of my postgres ? Is there something I need to do on my side?
j
No, not at all. And also no indication in the output I saw.
Best chance to figure that out really is
DEBUG=*
possible showing an error, or the link that creates the issue on Github.
t
I also got this one
I can create the issue on Github with the link if you want?
j
That would be nice, yes.
Also include that las tscreenshot!
That is indeed where it goes wrong.
No clear idea why though.
Maybe the issue will give more info.
j
Sweet, added the second screenshot as well and the original error message you posted here in this thread - and a link to here. Someone will look at the issue and possibly ask further questions trying to understand.
r
Hi everyone, not sure if this has been solved, but I’m facing the same issue now. The link to the code base that caused this issue is https://github.com/leerob/next-prisma