We had multiple users (3 so far) report that Prisma Studio fails while looking for this Checkpoint file of theirs (it is their telemetry).
I am not sure if this is only when migrating from Wasp 0.11 to 0.13, or for any Wasp version.
I am guessing once we upgrade to Prisma this will likely stop being an issue, but for now, I can confirm that disabling the Prisma Checkpoint thing solves the issue.
So I suggest that in Wasp we set CHECKPOINT_DISABLE=1 (the same way we set that env var for Prisma to stop warning people about upgrading), so from the next release on we don't have that issue.
Once we get Prisma to 5, we can see about removing this env var."
Martinsos
commented
3 weeks ago
We had multiple users (3 so far) report that Prisma Studio fails while looking for this Checkpoint file of theirs (it is their telemetry).
I am not sure if this is only when migrating from Wasp 0.11 to 0.13, or for any Wasp version.
I am guessing once we upgrade to Prisma this will likely stop being an issue, but for now, I can confirm that disabling the Prisma Checkpoint thing solves the issue.
So I suggest that in Wasp we set
CHECKPOINT_DISABLE=1(the same way we set that env var for Prisma to stop warning people about upgrading), so from the next release on we don't have that issue.Once we get Prisma to 5, we can see about removing this env var."
https://discord.com/channels/686873244791210014/1243865722698862664/1243865722698862664
https://discord.com/channels/686873244791210014/1240671340542038016/1240671340542038016