bozobit Comments - Answer Overflow

bozobit

•Created by bozobit on 1/27/2025 in #help-and-questions

Intermittent Server Error with Prisma 6.2.1 with Node 22 on Linux Mint

Ah! I figured it out. It turned out that this was a timeout error when connecting to a remote database that was far from me. I am in Auckland and the database was in the USA. Once I switched the database (Neon) to Sydney, the problem resolved itself. However, i will say that the error message from Prisma was not very helpful! (see above) I discovered the issue by trying with Drizzle and it gave me a timeout message. That was the key to figuring it out. 😃

8 replies

PPrisma

•Created by bozobit on 1/27/2025 in #help-and-questions

Intermittent Server Error with Prisma 6.2.1 with Node 22 on Linux Mint

@Nurul (Prisma) Well, after replacing my Linux Mint OS with the latest LTS of Ubuntu, the intermittent error remained. I then downgraded to 5.22.0 and the intermttent problem remained. But when I run the same configuration on Windows 11, no problem! I'm really stuck here, and after using Prisma for over 2 years, I've lost some confidence that it will behave predictably. I think I'm going to explore Drizzle.

8 replies

PPrisma

•Created by bozobit on 1/27/2025 in #help-and-questions

Intermittent Server Error with Prisma 6.2.1 with Node 22 on Linux Mint

@Nurul (Prisma). An update. I found that there may be incompatibiliites between Prisma and Linux Mint in dev? Will be swithing to Ubuntu to see if that addresses the issue. When I run the same NextJS application in Dev on Windows 11, no problems.

8 replies

PPrisma

•Created by bozobit on 1/27/2025 in #help-and-questions

Intermittent Server Error with Prisma 6.2.1 with Node 22 on Linux Mint

Thanks @Nural(Prisma), Well, I looked up disabling HMR and that looked more difficult, so I just separately did an pnpm build and then pnpm start to run the app without HMR. Then stringifying the error message gave me only an object like { digest: '520418415' } with no other information. At first caused it to error out every time. Then I regenerated prisma with npx prisma generate and then built and started again. After I did that, the intermittent problem stopped and I no longer get the error. I can now just run pnpm dev and use the HMR and it appears to be fine. I really have no idea what I did or what caused this, but I'm just afraid it will come back. (Well, it did the next day!) FYI, here is my package.json file that I hope answers your quesiton on how I'm including prisma.

{
  "name": "@repo/database",
  "version": "0.0.0",
  "main": "./index.ts",
  "types": "./index.ts",
  "scripts": {
    "analyze": "prisma generate --no-hints",
    "build": "prisma generate --no-hints",
    "clean": "git clean -xdf .cache .turbo dist node_modules",
    "typecheck": "tsc --noEmit --emitDeclarationOnly false"
  },
  "dependencies": {
    "@neondatabase/serverless": "^0.10.4",
    "@prisma/adapter-neon": "^6.2.1",
    "@prisma/client": "6.2.1",
    "@t3-oss/env-nextjs": "^0.11.1",
    "server-only": "^0.0.1",
    "undici": "^7.3.0",
    "ws": "^8.18.0",
    "zod": "^3.24.1"
  },
  "devDependencies": {
    "@repo/typescript-config": "workspace:*",
    "@types/node": "22.10.7",
    "@types/ws": "^8.5.14",
    "bufferutil": "^4.0.9",
    "prisma": "6.2.1",
    "typescript": "^5.7.3"
  }
}

8 replies

Gaming

Programming