Wasp•8mo ago

Broke wasp db studio after migrating from Wasp 0.11 to 0.13

Hi 👋 Wasp db studio seems to break after migrating from Wasp 0.11 to 0.13. I've followed the guide as outlined in the documentation, so I've first upgraded to 0.12 and afterwards to 0.13. However, when I now try to run wasp db studio I'm getting following error: Any idea on how to resolve this?

[   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/MY_USERNAME/Library/Caches/checkpoint-nodejs/.71912.0' -> '/Users/MY_USERNAME/Library/Caches/checkpoint-nodejs/prisma-studio-default'] {
[   Db  !]   errno: -2,
[   Db  !]   code: 'ENOENT',
[   Db  !]   syscall: 'rename',
[   Db  !]   path: '/Users/MY_USERNAME/Library/Caches/checkpoint-nodejs/.71912.0',
[   Db  !]   dest: '/Users/MY_USERNAME/Library/Caches/checkpoint-nodejs/prisma-studio-default'
[   Db  !] }
[   Db  !] 
[   Db  !] Node.js v20.3.0
Internal Wasp error (bug in compiler):
  This should never happen, studio should never stop.
  CallStack (from HasCallStack):
    error, called at cli/src/Wasp/Cli/Command/Db/Studio.hs:29:3 in waspc-0.13.2-inplace-cli-lib:Wasp.Cli.Command.Db.Studio

[   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/MY_USERNAME/Library/Caches/checkpoint-nodejs/.71912.0' -> '/Users/MY_USERNAME/Library/Caches/checkpoint-nodejs/prisma-studio-default'] {
[   Db  !]   errno: -2,
[   Db  !]   code: 'ENOENT',
[   Db  !]   syscall: 'rename',
[   Db  !]   path: '/Users/MY_USERNAME/Library/Caches/checkpoint-nodejs/.71912.0',
[   Db  !]   dest: '/Users/MY_USERNAME/Library/Caches/checkpoint-nodejs/prisma-studio-default'
[   Db  !] }
[   Db  !] 
[   Db  !] Node.js v20.3.0
Internal Wasp error (bug in compiler):
  This should never happen, studio should never stop.
  CallStack (from HasCallStack):
    error, called at cli/src/Wasp/Cli/Command/Db/Studio.hs:29:3 in waspc-0.13.2-inplace-cli-lib:Wasp.Cli.Command.Db.Studio

7 Replies

kapa.ai•8mo ago

Hi @WWWillems. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave: ---------------------- I'm sorry to hear that you're experiencing issues with wasp db studio after migrating from Wasp 0.11 to 0.13. Based on the error message you provided, it seems like there's an issue with renaming a file in your cache directory. This might be due to a bug in Prisma Studio, which is used by Wasp for the db studio command. There have been similar issues reported on the Wasp GitHub page, where Prisma Studio was unable to find the required engine binary, causing it to fail (source (https://github.com/wasp-lang/wasp/issues/228)). However, this was reported to be a bug in Prisma and was fixed in a newer version. Here are a few steps you can try to resolve this issue: 1. Clear the cache: The error message indicates a problem with a file in your cache directory. Try clearing the cache and then run the command again. 2. Update Prisma: Make sure you're using the latest version of Prisma. You can update Prisma by running npm i --save-dev prisma and npm i @prisma/client in your terminal (source (https://github.com/wasp-lang/wasp/issues/356)). 3. Reinstall Wasp: If the issue persists, try reinstalling Wasp to ensure you have the latest version and all dependencies are correctly installed. If none of these steps resolve your issue, I would recommend reporting this as a new issue on the Wasp GitHub page (https://github.com/wasp-lang/wasp/issues). Include the error message and any other relevant details to help the Wasp team diagnose the problem. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ---------------------- Sorry @WWWillems, 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?

WWWillemsOP•8mo ago

Hmz looks like I was able to resolve it by deleting the checkpoint-nodejs folder from ~/Library/Caches

martinsos•7mo ago

Hm that is weird! Checkpoint is Prisma's telemetry system, so this is sometihng on the Prisma side. Glad that you solved it! If you will have more issues with it in the future, you can turn off Prisma's telemetry by setting a certain env var, something like "CHECKPOINT_something" I can't remember exactly at the moment but you can find it in their docs.

CamBlackwood•7mo ago

I'm also seeing this on the same version of wasp, manually deleting cache solves issue

MEE6•7mo ago

Wohooo @CamBlackwood, you just became a Waspeteer level 3!

martinsos•7mo ago

Hm that is annoying than, seems everybody has it! @CamBlackwood was it for you also the case that you migrated from older to newer version of Wasp? After you delete that cache, does the issue ever appear again? Btw I did a bit of digging, so the quick solution is to set CHECKPOINT_DISABLE=1 env var in your bashrc or something. I will see that we add this to next Wasp release, and once Wasp upgrades to Prisma 5, I am assuming the problem will go away anyway.

CamBlackwood•7mo ago

Haven't done any migrations I don't think, and it's intermittent, similar to the OP - maybe every 3-4 times?

Gaming

Programming

Broke wasp db studio after migrating from Wasp 0.11 to 0.13