-
Notifications
You must be signed in to change notification settings - Fork 48
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
Comments
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 |
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? |
it happens all the time |
I was tried to uninstall and install it again, but the error was there |
there was one more error |
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 |
because of that, I also not able to store all data |
and same error was after all this script run |
I haven't tried it yet |
but still, I want to know by it happened. |
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. |
try to save 10,000 entries with the script you'll get timeout errors |
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. |
I am using this with next js |
so wherever I hit this route this script run automatically |
which save data one by one |
and haven't checked seeding, because I was following the YT tutorials |
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. |
I working on deferent project, will check later |
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". |
@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? |
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.
The text was updated successfully, but these errors were encountered: