Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

warn(prisma-client) Already 10 Prisma Clients are actively running. #800

Closed
yaojiach opened this issue Nov 15, 2021 · 4 comments
Closed
Assignees
Milestone

Comments

@yaojiach
Copy link

Describe the bug
warn(prisma-client) Already 10 Prisma Clients are actively running shows shortly after starting prisma studio from command line.

To Reproduce
Steps to reproduce the behavior:
Run prisma studio in a project with Prisma.
Warning shows shortly after.

Expected behavior
warn(prisma-client) Already 10 Prisma Clients are actively running should not show.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

  • OS: [e.g. iOS]: MacOS 12.01
  • Browser [e.g. chrome, safari]: Chrome
  • Version [e.g. 22]: 95.0.4638.69

Smartphone (please complete the following information):

  • Device: [e.g. iPhone6]
  • OS: [e.g. iOS8.1]
  • Browser [e.g. stock browser, safari]
  • Version [e.g. 22]

Additional context
Add any other context about the problem here.

@yaojiach yaojiach added the topic: hosted data browser It's about cloud.prisma.io label Nov 15, 2021
@janpio janpio removed the topic: hosted data browser It's about cloud.prisma.io label Nov 15, 2021
@bardsol
Copy link

bardsol commented Nov 30, 2021

I'm having the same issue after starting a new project recently. Only difference from this project is that I'm using a new database provider (supabase.com), I used digitalocean for the previous project.

This only happens if I'm using the live production database URL, if I'm using my local I don't get this warning.

Is there something related to supabase?

@janpio
Copy link
Contributor

janpio commented Nov 30, 2021

It is not, and is probably also not a problem for you at all - it is just an internal warning from the Prisma Client that Prisma Studio is using under the hood, that it opened more than 10 instances of that.

@yaojiach
Copy link
Author

@janpio thanks. hope it'll be resolved in future releases. really awesome tool to quickly access and manipulate data.

@eemmiillyy eemmiillyy self-assigned this Dec 29, 2021
@sdnts sdnts closed this as completed Jan 3, 2022
@sdnts sdnts reopened this Jan 3, 2022
@sdnts
Copy link
Contributor

sdnts commented Jan 6, 2022

This should be fixed on the latest Prisma CLI dev version (3.8.0-dev.46 as of writing). Could you update your CLI and let me know if you're still seeing this?
This will make it the stable CLI with the next release (next Tuesday). You can keep using the dev version if you'd like, but I'd recommend upgrading to 3.8.0 when it goes out, since dev versions are mostly for internal use and may contain unannounced breaking changes.

Let me know if you're still seeing this!

@sdnts sdnts closed this as completed Jan 6, 2022
@sdnts sdnts added this to the 3.8.0 milestone Jan 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants