You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm the maintainer of zeebe-node. I'm testing the grpc-js package as a replacement for the C-based client, since that one is being deprecated in April, 2021.
When connecting to Camunda Cloud, which uses a TLS-secured nginx proxy at the front-end, using the grpc-js library causes the process to exit with a segmentation fault.
It traced it with a debugger and it happens in Node's http2 module.
The same code, using the grpc package works with no problem.
Reproduction steps
If I run a test in my suite on Node 12.6.0 like this:
NODE_DEBUG=http2 NODE_DEBUG_NATIVE=tls,http2 GRPC_TRACE=channel,call_stream GRPC_VERBOSITY=DEBUG ZEEBE_NODE_LOGLEVEL=debug ZEEBE_NODE_PUREJS=true jest Worker-integration
A segmentation fault in Node is, in my view, unambiguously a bug in Node itself, so I suggest filing an issue against Node (https://github.com/nodejs/node). When you do so, you should probably include a C-level stacktrace, which can be obtained using a tool like gdb. Some code that reproduces the error would probably also help.
Problem description
I'm the maintainer of zeebe-node. I'm testing the grpc-js package as a replacement for the C-based client, since that one is being deprecated in April, 2021.
When connecting to Camunda Cloud, which uses a TLS-secured nginx proxy at the front-end, using the grpc-js library causes the process to exit with a segmentation fault.
It traced it with a debugger and it happens in Node's http2 module.
The same code, using the grpc package works with no problem.
Reproduction steps
If I run a test in my suite on Node 12.6.0 like this:
I get the following output:
On Node 13.14.0:
On Node 14.15.6:
Environment
The text was updated successfully, but these errors were encountered: