Wasp-lang•5mo ago

This should never happen, studio should never stop.

[   Db   ] Environment variables loaded from .env
[   Db   ] Prisma schema loaded from ../db/schema.prisma
[   Db   ] Prisma Studio is up on http://localhost:5555
[   Db  !] node:internal/process/promises:289
[   Db  !]             triggerUncaughtException(err, true /* fromPromise */);
[   Db  !]             ^
[   Db  !] 
[   Db  !] [Error: ENOENT: no such file or directory, rename '/Users/karankrishnani/Library/Caches/checkpoint-nodejs/.88641.0' -> '/Users/karankrishnani/Library/Caches/checkpoint-nodejs/prisma-studio-default'] {
[   Db  !]   errno: -2,
[   Db  !]   code: 'ENOENT',
[   Db  !]   syscall: 'rename',
[   Db  !]   path: '/Users/karankrishnani/Library/Caches/checkpoint-nodejs/.88641.0',
[   Db  !]   dest: '/Users/karankrishnani/Library/Caches/checkpoint-nodejs/prisma-studio-default'
[   Db  !] }
[   Db  !] 
[   Db  !] Node.js v20.12.2

[   Db   ] Environment variables loaded from .env
[   Db   ] Prisma schema loaded from ../db/schema.prisma
[   Db   ] Prisma Studio is up on http://localhost:5555
[   Db  !] node:internal/process/promises:289
[   Db  !]             triggerUncaughtException(err, true /* fromPromise */);
[   Db  !]             ^
[   Db  !] 
[   Db  !] [Error: ENOENT: no such file or directory, rename '/Users/karankrishnani/Library/Caches/checkpoint-nodejs/.88641.0' -> '/Users/karankrishnani/Library/Caches/checkpoint-nodejs/prisma-studio-default'] {
[   Db  !]   errno: -2,
[   Db  !]   code: 'ENOENT',
[   Db  !]   syscall: 'rename',
[   Db  !]   path: '/Users/karankrishnani/Library/Caches/checkpoint-nodejs/.88641.0',
[   Db  !]   dest: '/Users/karankrishnani/Library/Caches/checkpoint-nodejs/prisma-studio-default'
[   Db  !] }
[   Db  !] 
[   Db  !] Node.js v20.12.2

5 Replies

kapa.ai•5mo ago

Hi @Karan. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave: ---------------------- The error message you're seeing indicates that the system is unable to find or access a specific file or directory. This could be due to a variety of reasons such as the file or directory not existing, incorrect permissions, or the file or directory being in use by another process. However, without more context or information, it's difficult to provide a specific solution. The error could be related to the Prisma Studio setup or it could be an issue with your local environment. Here are a few general suggestions: 1. Ensure that the path /Users/karankrishnani/Library/Caches/checkpoint-nodejs/ exists and that your user has the correct permissions to access and modify it. 2. Try clearing your cache or deleting the .88641.0 and prisma-studio-default files if they exist, then restart Prisma Studio. 3. Ensure that you're using a compatible version of Node.js. Prisma supports Node.js versions 12, 14, and 16. 4. If you're using Wasp, ensure that your project's setup is correct. For example, the Prisma schema should be located in the db/ directory and the .env file should be correctly configured. You can refer to the Wasp documentation (https://wasp-lang.dev/docs) for more information. If none of these suggestions work, I recommend creating an issue in the Wasp Github repository (https://github.com/wasp-lang/wasp/issues) or asking for help in the Wasp Discord server (https://discord.com/channels/686873244791210014/1205728717993672705). Be sure to include the full error message and any relevant details about your setup. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ---------------------- Sorry @Karan, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist: Perhaps try again in 15mins?

Karan•5mo ago

Not sure what fixed this but I no longer have the issue

martinsos•5mo ago

THis is Prisma erroring out on their telemetry -> if it comes again, add CHECKPOINT_DISABLE=1 to your .bashrc or similar. This will disable Prisma from checking for updates (which we don't want anyway), and this error won't happen again.

Karan•5mo ago

Thanks, should this be added into the .env file?

martinsos•5mo ago

Best to just add it to .bashrc or similar! It should also go away with newer versions of Wasp

Gaming

Programming

This should never happen, studio should never stop.