Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

PANIC: no entry found for key in query-engine/prisma-models/src/record.rs:67:33

See original GitHub issue

Bug description

Invalid `prisma.product.findFirst()` invocation:


  PANIC: no entry found for key in query-engine/prisma-models/src/record.rs:67:33

This is a non-recoverable error which probably happens when the Prisma Query Engine has a panic.

When query data from database at runtime

How to reproduce

It’s happen randomly to resolve I’ve to redeploy layer that contain Prisma engine

Expected behavior

No response

Prisma information

Prisma query happen randomly

Environment & setup

OS: Linux on AWS Lambda
Database: PostgreSQL
Node.js version: 14 on Lambda

Prisma Version

3.13.0

Issue Analytics

State:
Created a year ago
Comments:11 (4 by maintainers)

Top GitHub Comments

1reaction

Weakkycommented, Jun 21, 2022

Is it possible that AWS Lambda running out of memory on runtime can cause this? This seems very very unlikely. You’d most likely get an OS error or something else if that was the case, not a user-created rust panic.

The panic happens because the QE tries to order by (in-memory) a field that does not exist. Given that we have no other issue with that panic and that you unfortunately can’t reproduce it either, I’m gonna close your issue for now since there’s not much more we can do.

If it ever happens again, please re-open that issue and let us know as much as you can.

Thanks for reporting 🙏

1reaction

wiput1999commented, Jun 21, 2022

Hi @Weakky ,

Thank you for following up on this issue. It never happened again since that day not sure why. Other things come to my mind I would like to ask. Is it possible that AWS Lambda running out of memory on runtime can cause this?