Closed Sheraff closed 1 year ago
prisma v4.9.0 => no error
prisma v4.12.0 => no segfault, but another non-descript error
0|soft-serve-tunes | 2023-04-23T18:08:09: prisma:error
0|soft-serve-tunes | 2023-04-23T18:08:09: Invalid `prisma.track.findMany()` invocation:
0|soft-serve-tunes | 2023-04-23T18:08:09:
0|soft-serve-tunes | 2023-04-23T18:08:09:
0|soft-serve-tunes | 2023-04-23T18:08:09: Server has closed the connection.
same error on v4.13.0 (and also no segfault this time...)
prisma v4.11.0 => no error
New interesting error on 4.13
0|soft-serve-tunes | 2023-04-25T13:35:55: prisma:error
0|soft-serve-tunes | 2023-04-25T13:35:55: Invalid `prisma.album.findMany()` invocation:
0|soft-serve-tunes | 2023-04-25T13:35:55:
0|soft-serve-tunes | 2023-04-25T13:35:55:
0|soft-serve-tunes | 2023-04-25T13:35:55: Error opening a TLS connection: error:24067044:random number generator:rand_pool_add:internal error:crypto/rand/rand_lib.c:733:
$ npx prisma version
Environment variables loaded from .env
prisma : 4.13.0
@prisma/client : 4.13.0
Current platform : linux-arm64-openssl-1.1.x
Query Engine (Node-API) : libquery-engine 1e7af066ee9cb95cf3a403c78d9aab3e6b04f37a (at node_modules/@prisma/engines/libquery_engine-linux-arm64-openssl-1.1.x.so.node)
Migration Engine : migration-engine-cli 1e7af066ee9cb95cf3a403c78d9aab3e6b04f37a (at node_modules/@prisma/engines/migration-engine-linux-arm64-openssl-1.1.x)
Format Wasm : @prisma/prisma-fmt-wasm 4.13.0-50.1e7af066ee9cb95cf3a403c78d9aab3e6b04f37a
Default Engines Hash : 1e7af066ee9cb95cf3a403c78d9aab3e6b04f37a
Studio : 0.484.0
Preview Features : extendedWhereUnique
Waiting on prisma versions. Closing this PR as it will not be used, main branch has been reverted to prisma 4.9
App has been throwing segfaults on start since upgrading major packages (next, trpc, prisma, next-auth). This PR aims at finding the guilty package and reverting to a stable version.
Apparently it might be coming from Prisma (https://github.com/prisma/prisma/issues/18510). So I'm trying versions between 4.9 (never seen the issue), and 4.13 (first time seeing the issue, never tried versions in between).
prisma version (taken after a bunch of re-installs, at a time where I don't reproduce the segfault anymore...). But still, it was on 4.13 that I got the error, and that was at a 1-hour interval max on a sunday so hopefully it's the same exact version.