Clinic doesn't start load testing ghz process with "--on-port" option

Hello Guys, maybe someone able to give me an advice with the issue.

I try some experiments with using of Clinic.js Flame tool for performance optimization of our gRPC server. I try to follow the official tutorial but change autocanon with ghz. It works as expected when I run ghz and Clinic as independent processes in different terminal sessions, however hangs indefinitely when I try to combine them both in one command with '--on-port' option.

Expected Behavior

Execution of the command (Windows terminal)

clinic flame --on-port^
 'ghz --insecure -n 1000 --proto ./proto/notes.proto --call myTestService.TestService.List 0.0.0.0:50051 '^
 -- node runTestServer.js

should automatically start ghz, wait for its finish and then open a new flamegraph in browser. Please note that both server and ghz command are correct as if I run them manually in separate terminal processes they work as expected and generate a new flamegraph.

Current Behavior

It starts the test gRPC server and then stuck forever. It requires multiple Ctrl+C to terminate process, flamegraph isn't generated. Seems that ghz process never starts. My guess is that Clinic flame fails to detect an opened port from the testServer.js and never starts ghz, but I am not sure of how to prove it.

Steps to Reproduce (for bugs)

Grab some Node.js gRPC server app.
Install ghz on your machine.
Run the standard clinic flame command as described above.
The command stuck forever after running the server but before calling the ghz.

Environment

Clinic v12.0.0, clinic flame v12.0.0 (0x v5.4.1), OS Windows 10 Pro

Thanks, Peter

clinicjs / node-clinic