Mika
Mika
PPrisma
Created by Mika on 4/26/2025 in #help-and-questions
Missing field enableTracing
I'm having a problem with prisma in the production server. It is working fine locally Error:
thread '<unnamed>' panicked at query-engine/query-engine-node-api/src/engine.rs:76:45:

Failed to deserialize constructor options.

This usually happens when the javascript object passed to the constructor is missing
properties for the ConstructorOptions fields that must have some value.

If you set some of these in javascript through environment variables, make sure there are
values for data_model, log_level, and any field that is not Option<T>
: Error { status: InvalidArg, reason: "missing field `enableTracing`", maybe_raw: 0x0 }
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
fatal runtime error: failed to initiate panic, error 5
thread '<unnamed>' panicked at query-engine/query-engine-node-api/src/engine.rs:76:45:

Failed to deserialize constructor options.

This usually happens when the javascript object passed to the constructor is missing
properties for the ConstructorOptions fields that must have some value.

If you set some of these in javascript through environment variables, make sure there are
values for data_model, log_level, and any field that is not Option<T>
: Error { status: InvalidArg, reason: "missing field `enableTracing`", maybe_raw: 0x0 }
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
fatal runtime error: failed to initiate panic, error 5
8 replies