Application error after v0.8.0 upgrade

[huijing]

I just deployed v0.8.0 to Heroku and the application crashed with the following error:

2020-10-07T23:38:39.557142+00:00 app[web.1]: node[23]: ../src/node_http_parser_impl.h:529:static void node::{anonymous}::Parser::Initialize(const v8::FunctionCallbackInfo<v8::Value>&): Assertion `args[3]->IsInt32()' failed.
2020-10-07T23:38:39.557762+00:00 app[web.1]: 1: 0xa17c40 node::Abort() [node]
2020-10-07T23:38:39.558341+00:00 app[web.1]: 2: 0xa17cbe  [node]
2020-10-07T23:38:39.558840+00:00 app[web.1]: 3: 0xa3214a  [node]
2020-10-07T23:38:39.559363+00:00 app[web.1]: 4: 0xc019e9  [node]
2020-10-07T23:38:39.559906+00:00 app[web.1]: 5: 0xc037d7 v8::internal::Builtin_HandleApiCall(int, unsigned long*, v8::internal::Isolate*) [node]
2020-10-07T23:38:39.560665+00:00 app[web.1]: 6: 0x1409319  [node]
2020-10-07T23:38:39.564593+00:00 app[web.1]: Aborted

It might be related to this issue: prisma/prisma-client-js#907

[mikecao]

Which version did you upgrade from? The prisma upgrade was several releases back.

[hemorej]

I'm getting the same even with prisma 2.7 (release 0.54)

Update: It might be the node version breaking everything actually. I'm all the way back at 0.32 with prisma 2.6 and still getting the same error

0|umami  | node[5949]: ../src/node_http_parser_impl.h:529:static void node::{anonymous}::Parser::Initialize(const v8::FunctionCallbackInfo<v8::Value>&): Assertion `args[3]->IsInt32()' failed.
0|umami  |  1: 0xa17c40 node::Abort() [node]
0|umami  |  2: 0xa17cbe  [node]
0|umami  |  3: 0xa3214a  [node]
0|umami  |  4: 0xc019e9  [node]
0|umami  |  5: 0xc037d7 v8::internal::Builtin_HandleApiCall(int, unsigned long*, v8::internal::Isolate*) [node]
0|umami  |  6: 0x1409319  [node]
0|umami  | Aborted (core dumped)
0|umami  | npm 
0|umami  | ERR! code ELIFECYCLE
0|umami  | npm ERR! errno 134
0|umami  | npm ERR! umami@0.32.0 start: `next start`
0|umami  | npm ERR! Exit status 134
0|umami  | npm ERR! 
0|umami  | npm ERR! Failed at the umami@0.32.0 start script.
0|umami  | npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

[huijing]

I upgraded from 0.7.4 (which deployed and ran without issue)

[hemorej]

@huijing what's your node version?

[huijing]

Oh I just checked the build logs, the latest deploy ran on node version 12.19.0 instead of the previous 12.18.14
In that case, I guess this is not a umami issue per se, it's that prisma issue they need to resolve on their end
Should I close this issue then?

[hemorej]

I guess. But just in case anyone is looking for a temporary fix, downgrading to node 12.18.4 works

[huijing]

Closing because not an umami issue. Folks running into similar issues can follow @hemorej's tip to downgrade node.

[Jolg42]

The next version of Prisma will include the fix 😉
prisma/prisma-client-js#907