This repository has been archived by the owner on Jan 14, 2021. It is now read-only.
Queries and mutations stuck (runs forever?) if log option is ['query', 'warn'] #714
Labels
bug/2-confirmed
We have confirmed that this is a bug.
kind/regression
A reported bug in functionality that used to work before.
tech/typescript
Issue for tech TypeScript.
Milestone
Comments
I can confirm this bug. We need to address this pretty quickly. Reproduction:
Debug trace:
|
pantharshit00
added
bug/2-confirmed
We have confirmed that this is a bug.
kind/regression
A reported bug in functionality that used to work before.
labels
Jun 5, 2020
timsuchanek
added a commit
to prisma/prisma
that referenced
this issue
Jun 5, 2020
Thanks a lot for reporting 🙏 In case it’s not fixed for you - please let us know and we’ll reopen this issue! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
bug/2-confirmed
We have confirmed that this is a bug.
kind/regression
A reported bug in functionality that used to work before.
tech/typescript
Issue for tech TypeScript.
Bug description
When the log option for the Prisma client is set to ['query', 'warn'] i.e without the
info
option or ['warn'] i.e withoutquery
andinfo
, all queries and mutations get stuck at the first call to the client. Using the three options or any of the other two alone or together works fine but thewarn
option seems to only work wheninfo
is also set.Is this a bug or the expected behavior? If it is the expected behavior, can we make this clear in the docs?
`
How to reproduce
Steps to reproduce the behavior:
Expected behavior
['query', 'warn'] and ['warn'] log options should work without the
info
optionPrisma information
Environment & setup
The text was updated successfully, but these errors were encountered: