PANIC: called `Option::unwrap()` on a `None` value in query-engine/core/src/query_document/parser.rs:250:87

Hi Prisma Team! My Prisma Client just crashed. This is the report: This happened after I added the nApi previewFeature. I’m also using a PaaS to deploy. I have no info about their server config. I had no issues on own PC.

Versions

Name	Version
Node	v14.15.0
OS	debian-openssl-1.1.x
Prisma Client	2.26.0
Query Engine	0.1.0
Database	mysql

Query

{"X":{}}

Logs

    at LibraryEngine.logger (/app/node_modules/@prisma/client/runtime/index.js:22751:32)
    at /app/node_modules/@prisma/client/runtime/index.js:22721:36
prisma:client:napi sending request, this.libraryStarted: true
prisma:client:napi library already starting, this.libraryStarted: true
prisma:client:napi graphQLToJSError
prisma:client:fetcher Error: called `Option::unwrap()` on a `None` value
    at LibraryEngine.prismaGraphQLToJSError (/app/node_modules/@prisma/client/runtime/index.js:22870:14)
    at LibraryEngine.request (/app/node_modules/@prisma/client/runtime/index.js:22885:24)
    at async cb (/app/node_modules/@prisma/client/runtime/index.js:33866:26)
    at async Object.exports.updateUser (/app/modules/users/model.js:51:20)
    at async exports.updateUser (/app/modules/users/controller.js:44:20)

Client Snippet

const user = await db.user.findFirst({
      where: {
        deleted: {
          equals: false,
        },
        OR: [
          {
            email: {
              equals: email,
            },
          },
          {
            username: {
              equals: email,
            },
          },
        ],
      },
      select: {
        id: true,
        avatar: true,
        username: true,
        email: true,
        password: true,
        profile_completed: true,
        profession: true,
        email_verified: true,
        bio: true,
        social_media: true,
        header_img: true,
        full_name: true,
      },
    });

Schema

model User {
  id                Int              @id @default(autoincrement())
  username          String           @unique @db.VarChar(255)
  email             String           @unique @db.VarChar(255)
  password          String           @db.VarChar(255)
  created_at        DateTime         @default(now()) @db.DateTime(6)
  updated_at        DateTime         @updatedAt
  deleted           Boolean          @default(false)
  type              Roles            @default(USER)
  avatar            String?          @db.VarChar(250)
  header_img        String?          @db.VarChar(250)
  bio               String?          @db.Text
  full_name         String?          @db.VarChar(250)
  posts             Post[]           @relation(name: "posts")
  likes             Likes[]          @relation(name: "userLikes")
  bookmarks         Bookmarks[]      @relation(name: "userBookmarks")
  comments          Comments[]
  commentLikes      commentLikes[]
  commentReplies    commentReplies[]
  pollVotes         PollVotes[]
  verified          Boolean          @default(false)
  email_verified    Boolean          @default(false)
  profile_completed Boolean          @default(false)
  social_media      Json?

  @@index([email, username])
  @@map("users")
}

[janpio]

Can you maybe open a new issue about this and provide all the information it asks for? Optimal would be some code for us to easily reproduce the error. Assume we don’t know much about how to use nodemon or how it works. Super eager to look into this!

[pantharshit00]

I will close this for as I can’t reproduce this NAPI as well with 2.28. Please let us know if this happens again.

Hosting platform shouldn’t matter here.