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

A non-recoverable error has occurred and Studio has to be restarted. #989

Open
mrseankumar25 opened this issue Jul 25, 2022 · 23 comments
Open
Labels
bug/0-unknown Bug is new, does not have information for reproduction or reproduction could not be confirmed. kind/bug A reported bug.

Comments

@mrseankumar25
Copy link

mrseankumar25 commented Jul 25, 2022

A non-recoverable error has occurred and Studio has to be restarted. Please consider reporting this error to us by opening an issue on GitHub and attaching the error details. If this persists, please clear out your IndexedDB and try again.

@petradonka
Copy link
Contributor

Hello,

If you're still running into issues, please provide a few more details by filling in the original issue with information such as the version you're using, relevant logs, and the steps that are leading to what you're seeing.

Thank you!

@mrseankumar25
Copy link
Author

mrseankumar25 commented Jul 25, 2022

Hello,

If you're still running into issues, please provide a few more details by filling in the original issue with information such as the version you're using, relevant logs, and the steps that are leading to what you're seeing.

Thank you!

Hi @petradonka

Thank you for the response, I am using 4.x something, this is after I added around 130000 in one table and 250000 around in another one. The above-mentioned error is come up in the studio client as a popup. By the way, I am using the SQLite database.

thank you

@petradonka
Copy link
Contributor

Thanks for the additional info!

Have you tried clearing out your IndexedDB? See #895 (comment)

If the issue still exists, could you give us a bit more info on what steps you took that lead you to it? Does it always happen, or only sometimes?

The error popup in Studio you mentioned might have more logs, if that's the case, could you share those as well?

@petradonka petradonka reopened this Jul 25, 2022
@mrseankumar25
Copy link
Author

it happens all the time

@mrseankumar25
Copy link
Author

I was tried to uninstall and install it again, but the error was there

@mrseankumar25
Copy link
Author

there was one more error

@mrseankumar25
Copy link
Author

since I have very big data, I created a script to add data to my database, in the process I got so many timeout errors

@mrseankumar25
Copy link
Author

because of that, I also not able to store all data

@mrseankumar25
Copy link
Author

and same error was after all this script run
before that everything was working fine

@mrseankumar25
Copy link
Author

Thanks for the additional info!

Have you tried clearing out your IndexedDB? See #895 (comment)

If the issue still exists, could you give us a bit more info on what steps you took that lead you to it? Does it always happen, or only sometimes?

The error popup in Studio you mentioned might have more logs, if that's the case, could you share those as well?

I haven't tried it yet

@mrseankumar25
Copy link
Author

but still, I want to know by it happened.

@petradonka
Copy link
Contributor

You mentioned that you got timeout errors: are you using the Prisma Data Platform, or did you get timeout errors from your database directly?

Do you see any additional logs in the error popup in Studio? There should be a little arrow that allows you to expand the section that includes more logs and information about the error you're encountering.

@mrseankumar25
Copy link
Author

this is the script I used to save data, in the console I got a time-out error.

image

@mrseankumar25
Copy link
Author

try to save 10,000 entries with the script you'll get timeout errors

@petradonka petradonka added bug/0-unknown Bug is new, does not have information for reproduction or reproduction could not be confirmed. kind/bug A reported bug. team/developer-productivity labels Jul 25, 2022
@petradonka
Copy link
Contributor

How exactly is the script that you shared being run? You could also have a look at our documentation for seeding your database: https://www.prisma.io/docs/guides/database/seed-database

Have you had a chance to see if there are additional logs in the error popup in Studio? That'd be very helpful for us to understand what is happening.

@mrseankumar25
Copy link
Author

I am using this with next js

@mrseankumar25
Copy link
Author

so wherever I hit this route this script run automatically

@mrseankumar25
Copy link
Author

which save data one by one

@mrseankumar25
Copy link
Author

and haven't checked seeding, because I was following the YT tutorials

@petradonka
Copy link
Contributor

Got it, thanks for the additional info on the script.

Let's focus on getting the Studio error sorted first. Do you see any additional logs in the error popup in Studio? We'll need a bit of additional info to be able to look into this, and those logs would likely provide some clues as to what's going wrong.

@mrseankumar25
Copy link
Author

I working on deferent project, will check later

@Erbros
Copy link

Erbros commented Aug 4, 2022

Okay, so I got the same error on Prisma Studio, but it said there was something wrong with "count". Hadn't changed anything in the studio for ages, but suddenly remembered I moved the .env variables to .env.local a few days ago. Moved the Prisma related ones back and it was back again.

Before that I had tried restarting the computer, updating to 4.1.1 in prisma client and nothing worked. Not sure if this was an outcast and the studio already does this, but if the Studio can't find the env-variables it would be good to say so in the error.

Also not really sure if this is the same error, but I also got the "A non-recoverable error has occurred and Studio has to be restarted".

@petradonka
Copy link
Contributor

@Erbros, the env var issue looks unrelated, even if it results in a similar looking error. Could you open an issue for that, maybe with some additional information on how to reproduce the issue you ran into?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug/0-unknown Bug is new, does not have information for reproduction or reproduction could not be confirmed. kind/bug A reported bug.
Projects
None yet
Development

No branches or pull requests

4 participants