Serhii Tatarintsev

Hi @darkv ! We've identified and fixed the issue. Could you try dev snapshot version `5.18.0-integration-fix-config-dir-client.5` and see if the problem still happens for you? We don't recommend using dev...

@Aloysius999 what's Prisma query you are executing and what do you expect it to return?

You provided query does not match the schema you posted and you provided response does not match the query you are showing us either. Could you please go back to...

Hey @Aloysius999 , With the lack of information and our inability to reproduce this issue, we're now closing it. Feel free to comment if you have any updates about it....

For future reference, not confirmed yet: problem seems to be in `nodejs.util.inspect.custom` symbol we are using to have our Proxies displayed in Node's properly. It seems like making it non-enumerable...

Hi @bbhxwl! Please, fill out the issue template. Without this information there is no way for us to reproduce the issue and we'll have to close it. Thank you!

Hey @bbhxwl , With the lack of information and our inability to reproduce this issue, we're now closing it. Feel free to comment if you have any updates about it....

`@opentelemetry/[email protected]` has this generic and `@opentelemetry/[email protected]` does not. Looks like we were too generous with our version ranges (but also, looks look otel people did a breaking change in semver-minor)....

Hey @roxxel , Did you get a chance to have a look at my collegues comment? It'd be helpful for us to move your issue forward. Without further information, we'll...

Hi @zshannon. Unfortunately, I can not reproduce your issue: ```prisma datasource db { provider = "sqlite" url = "file:dev.db" } model Property { id Int @id @default(autoincrement()) key String value...