Prisma•2mo ago

Getting an error thread 'tokio-runtime-worker' panicked at libs/user-facing-errors/src/quaint.rs

Hi, Help! I started getting this error on production and not sure where it's coming from. The logs say to add RUST_BACKTRACE=1 Would that be in on my api server, like so? RUST_BACKTRACE=1 node src/ Just want to get some input / ideas before I start missing with the prod server. Logs: 2025-02-21T13:54:08.001644955Z thread 'tokio-runtime-worker' panicked at libs/user-facing-errors/src/quaint.rs:178:18: 2025-02-21T13:54:08.002582171Z internal error: entered unreachable code 2025-02-21T13:54:08.002592830Z note: run with RUST_BACKTRACE=1 environment

9 Replies

Prisma AI Help•2mo ago

You're in no rush, so we'll let a dev step in. Enjoy your coffee, or drop into #ask-ai if you get antsy for a second opinion!

jdkdevOP•2mo ago

Any help on this would be much appreciated... My research pointed me to the fact that adding the RUST_BACKTRACE flag would not work at the node process level

Nurul•2mo ago

Hey 👋 When exactly do you get this error? Does it happen randomly while trying to run a prisma query? Is this happening on latest version of prisma?

jdkdevOP•2mo ago

Hi @Nurul (Prisma) !

prisma                  : 5.15.0
@prisma/client          : 5.15.0
Computed binaryTarget   : debian-openssl-1.1.x
Operating System        : linux
Architecture            : x64
Node.js                 : v20.18.0
Query Engine (Node-API) : libquery-engine 12e25d8d06f6ea5a0252864dd9a03b1bb51f3022 (at node_modules/prisma/node_modules/@prisma/engines/libquery_engine-debian-openssl-1.1.x.so.node)
Schema Engine           : schema-engine-cli 12e25d8d06f6ea5a0252864dd9a03b1bb51f3022 (at node_modules/prisma/node_modules/@prisma/engines/schema-engine-debian-openssl-1.1.x)
Schema Wasm             : @prisma/prisma-schema-wasm 5.15.0-29.12e25d8d06f6ea5a0252864dd9a03b1bb51f3022
Default Engines Hash    : 12e25d8d06f6ea5a0252864dd9a03b1bb51f3022
Studio                  : 0.501.0

prisma                  : 5.15.0
@prisma/client          : 5.15.0
Computed binaryTarget   : debian-openssl-1.1.x
Operating System        : linux
Architecture            : x64
Node.js                 : v20.18.0
Query Engine (Node-API) : libquery-engine 12e25d8d06f6ea5a0252864dd9a03b1bb51f3022 (at node_modules/prisma/node_modules/@prisma/engines/libquery_engine-debian-openssl-1.1.x.so.node)
Schema Engine           : schema-engine-cli 12e25d8d06f6ea5a0252864dd9a03b1bb51f3022 (at node_modules/prisma/node_modules/@prisma/engines/schema-engine-debian-openssl-1.1.x)
Schema Wasm             : @prisma/prisma-schema-wasm 5.15.0-29.12e25d8d06f6ea5a0252864dd9a03b1bb51f3022
Default Engines Hash    : 12e25d8d06f6ea5a0252864dd9a03b1bb51f3022
Studio                  : 0.501.0

It's happening randomly about 1-2 times a day on production, can't reproduce it on dev.

Nurul•2mo ago

Can you upgrade to latest version and check if it still happens?

jdkdevOP•2mo ago

okay, I'll do that after-hours and report back. To confirm, is there any way for me to get the stack trace by adding something in node process?

Nurul•2mo ago

I would recommend setting DEBUG environment variable to see if you get additional information: https://www.prisma.io/docs/orm/prisma-client/debugging-and-troubleshooting/debugging#setting-the-debug-environment-variable

Debugging (Reference) | Prisma Documentation

This page explains how to enable debugging output for Prisma Client by setting the DEBUG environment variable.

jdkdevOP•2mo ago

good idea,
I upgraded prisma on production last night, and will update the thread if the error comes back. And will try the debug too Issue has not come back up... we can close this out!

Nurul•2mo ago

Thank you for getting back. I am glad to hear that 🙂

Gaming

Programming

Getting an error thread 'tokio-runtime-worker' panicked at libs/user-facing-errors/src/quaint.rs

Did you find this page helpful?