vidalab
November 19, 2020, 2:24am
1
Hello,
I’m running into a problem with my deployment. It has been working fine until today. I didn’t make any changes to my deployment prior to the problem.
I checked the lambda function graphql log and find the following error:
6:17:46 PM: /var/lang/bin/node[7]: ../src/node_http_parser_impl.h:529:static void node::{anonymous}::Parser::Initialize(const v8::FunctionCallbackInfo<v8::Value>&): Assertion `args[3]->IsInt32()' failed.
6:17:46 PM: 1: 0x55e6c86f71a3 node::Abort() [/var/lang/bin/node]
6:17:46 PM: 2: 0x55e6c86f7232 [/var/lang/bin/node]
6:17:46 PM: 3: 0x55e6c8715564 [/var/lang/bin/node]
6:17:46 PM: 4: 0x55e6c891a0a6 [/var/lang/bin/node]
6:17:46 PM: 5: 0x55e6c891bde1 v8::internal::Builtin_HandleApiCall(int, unsigned long*, v8::internal::Isolate*) [/var/lang/bin/node]
6:17:46 PM: 6: 0x55e6c91ba519 [/var/lang/bin/node]
6:17:46 PM: Duration: 347.30 ms Memory Usage: 123 MB
6:17:46 PM: RequestId: a489e74c-c307-40e6-8535-6bffa5d24b77 Error: Runtime exited with error: signal: aborted (core dumped)
Runtime.ExitError
My app uses redwoodjs. I found a suggestion from the redwoodjs community to use nodejs v12.18.4. But it doesn’t solve my problem.
opened 01:09PM - 09 Oct 20 UTC
closed 04:08AM - 14 Oct 20 UTC
topic/prisma
bug/confirmed
### What?
As of Redwood v19.x, data migrations are failing due to a low level N… ode.js error when running on Node v12.19.0
```
./src/node_http_parser_impl.h:529:static void node::(anonymous namespace)::Parser::Initialize(const FunctionCallbackInfo<v8::Value> &): Assertion `args[3]->IsInt32()' failed.
1: 0x1011f40c5 node::Abort() (.cold.1) [/Users/dac09/.nvm/versions/node/v12.19.0/bin/node]
2: 0x1000a5749 node::Abort() [/Users/dac09/.nvm/versions/node/v12.19.0/bin/node]
3: 0x1000a55b1 node::Assert(node::AssertionInfo const&) [/Users/dac09/.nvm/versions/node/v12.19.0/bin/node]
4: 0x1000c6e1b node::(anonymous namespace)::Parser::Initialize(v8::FunctionCallbackInfo<v8::Value> const&) [/Users/dac09/.nvm/versions/node/v12.19.0/bin/node]
5: 0x100259838 v8::internal::FunctionCallbackArguments::Call(v8::internal::CallHandlerInfo) [/Users/dac09/.nvm/versions/node/v12.19.0/bin/node]
6: 0x100258df9 v8::internal::MaybeHandle<v8::internal::Object> v8::internal::(anonymous namespace)::HandleApiCallHelper<false>(v8::internal::Isolate*, v8::internal::Handle<v8::internal::HeapObject>, v8::internal::Handle<v8::internal::HeapObject>, v8::internal::Handle<v8::internal::FunctionTemplateInfo>, v8::internal::Handle<v8::internal::Object>, v8::internal::BuiltinArguments) [/Users/dac09/.nvm/versions/node/v12.19.0/bin/node]
7: 0x100258562 v8::internal::Builtin_Impl_HandleApiCall(v8::internal::BuiltinArguments, v8::internal::Isolate*) [/Users/dac09/.nvm/versions/node/v12.19.0/bin/node]
```
This is a problem because Netlify uses 12.9 by default for builds.
### How to reproduce?
Run ```yarn rw dataMigrate up``` if you're running Node 12.9. Or simply push to netlify to build, as long as data migrate is part of the build command
### Workaround
The issue seems to be in prisma client > undici > node 12.9.0
Easy fix for now is to downgrade to node 12.8 OR upgrade to node stable (currrently 14).
In mycase, ~~I changed the value in .nvmrc to "stable"~~ (note: "stable" has been deprecated. See [this comment](https://github.com/redwoodjs/redwood/issues/1313#issuecomment-706443974) for workaround.)
### Todo
- [x] Reproduce on other projects
- [x] Identify where the issue is coming from
- [x] Propose workaround
fool
November 29, 2020, 10:48pm
2
Hiya @vidalab ! Sorry to say our Support team doesn’t know anything about redwood and this is something specific to that plugin, so hopefully that team can help you out further with this issue.