`Invalid coercion encountered: ConversionFailure("Float(BigDecimal(\"10.2\"))", "Decimal")`

Hi Prisma Team! My Prisma Client just crashed. This is the report:

Versions

Name	Version
Node	v14.8.0
OS	darwin
Prisma Client	2.24.1
Query Engine	query-engine 18095475d5ee64536e2f93995e48ad800737a9e4
Database	undefined

Query

mutation {
  createOnecorresponding_grams(data: {
    calories: 5
    plan: "X"
    size: 5
  }) {
    calories
    plan
    size
  }
}

Logs

template%3Dbug_report.md%0A++prisma%3Aclient+%0A++prisma%3Aclient+If+you+want+the+Prisma+team+to+look+into+it%2C+please+open+the+link+above+%F0%9F%99%8F%0A++prisma%3Aclient+To+increase+the+chance+of+success%2C+please+post+your+schema+and+a+snippet+of%0A++prisma%3Aclient+how+you+used+Prisma+Client+in+the+issue.+%0A++prisma%3Aclient+%0A++prisma%3Aclient+++++at+NodeEngine.throwAsyncErrorIfExists+%28%2FUsers%2Fyazid%2Fworkspace%2Felmut_app_v3%2Felmut_backend%2Fnode_modules%2F%40prisma%2Fclient%2Fruntime%2Findex.js%3A28354%3A21%29%0A++prisma%3Aclient+++++at+NodeEngine.handleRequestError+%28%2FUsers%2Fyazid%2Fworkspace%2Felmut_app_v3%2Felmut_backend%2Fnode_modules%2F%40prisma%2Fclient%2Fruntime%2Findex.js%3A27668%3A14%29%0A++prisma%3Aclient+++++at+runMicrotasks+%28%3Canonymous%3E%29%0A++prisma%3Aclient+++++at+processTicksAndRejections+%28internal%2Fprocess%2Ftask_queues.js%3A93%3A5%29%0A++prisma%3Aclient+++++at+NodeEngine.request+%28%2FUsers%2Fyazid%2Fworkspace%2Felmut_app_v3%2Felmut_backend%2Fnode_modules%2F%40prisma%2Fclient%2Fruntime%2Findex.js%3A28288%3A9%29%0A++prisma%3Aclient+++++at+cb+%28%2FUsers%2Fyazid%2Fworkspace%2Felmut_app_v3%2Felmut_backend%2Fnode_modules%2F%40prisma%2Fclient%2Fruntime%2Findex.js%3A35193%3A26%29++%0A++prisma%3Aengine+%7B%0A++prisma%3Aengine+++error%3A+Error%3A+connect+ECONNREFUSED+127.0.0.1%3A57100%0A++prisma%3Aengine+++++++at+TCPConnectWrap.afterConnect+%5Bas+oncomplete%5D+%28net.js%3A1144%3A16%29+%7B%0A++prisma%3Aengine+++++errno%3A+-61%2C%0A++prisma%3Aengine+++++code%3A+%27ECONNREFUSED%27%2C%0A++prisma%3Aengine+++++syscall%3A+%27connect%27%2C%0A++prisma%3Aengine+++++address%3A+%27127.0.0.1%27%2C%0A++prisma%3Aengine+++++port%3A+57100%0A++prisma%3Aengine+++%7D%0A++prisma%3Aengine+%7D++%0A%60%60%60%0A%0A%23%23+Client+Snippet%0A%60%60%60ts%0A%2F%2F+PLEASE+FILL+YOUR+CODE+SNIPPET+HERE%0A%60%60%60%0A%0A%23%23+Schema%0A%60%60%60prisma%0A%2F%2F+PLEASE+ADD+YOUR+SCHEMA+HERE+IF+POSSIBLE%0A%60%60%60%0A&title=PANIC+in+libs%2Fprisma-models%2Fsrc%2Frecord.rs%3A161%3A30%0AInvalid+coercion+encountered%3A+ConversionFailure%28%22Float%28BigDecimal%28%5C%221652%5C%22%29%29%22%2C+%22Decimal%22%29&template=bug_report.md
  prisma:client 
  prisma:client If you want the Prisma team to look into it, please open the link above 🙏
  prisma:client To increase the chance of success, please post your schema and a snippet of
  prisma:client how you used Prisma Client in the issue. 
  prisma:client 
  prisma:client     at NodeEngine.throwAsyncErrorIfExists (/Users/yazid/workspace/elmut_app_v3/elmut_backend/node_modules/@prisma/client/runtime/index.js:28354:21)
  prisma:client     at NodeEngine.handleRequestError (/Users/yazid/workspace/elmut_app_v3/elmut_backend/node_modules/@prisma/client/runtime/index.js:27668:14)
  prisma:client     at NodeEngine.request (/Users/yazid/workspace/elmut_app_v3/elmut_backend/node_modules/@prisma/client/runtime/index.js:28288:20)
  prisma:client     at runMicrotasks (<anonymous>)
  prisma:client     at processTicksAndRejections (internal/process/task_queues.js:93:5)
  prisma:client     at cb (/Users/yazid/workspace/elmut_app_v3/elmut_backend/node_modules/@prisma/client/runtime/index.js:35193:26)  
  prisma:engine { cwd: '/Users/yazid/workspace/elmut_app_v3/elmut_backend/src/prisma' }  
  prisma:engine Search for Query Engine in /Users/yazid/workspace/elmut_app_v3/elmut_backend/node_modules/.prisma/client  
  plusX Execution permissions of /Users/yazid/workspace/elmut_app_v3/elmut_backend/node_modules/.prisma/client/query-engine-darwin are fine  
  prisma:engine { flags: [ '--enable-raw-queries', '--port', '57104' ] }  
  prisma:engine stdout  Starting a postgresql pool with 13 connections.  
  prisma:engine stdou

[butofleury]

Any news on that? I have the similar issue with sql server. I’m using prisma 3.11.1. I tried also with 3.12.0-dev.43.

[SevInf]

Fixed by prisma/prisma-engines#2988 back in 4.0.0 and does not reproduce anymore.