process.on('exit', ... always errors

[anishkny]

Doesn't the following line mean that the process will always end in an error?

functions-framework-nodejs/src/invoker.ts

Line 531 in 518f2d0

logAndSendError(new Error(`Process exited with code ${code}`), latestRes);

What is the non-error-producing recommended way to stop the server? Say after testing in a CI environment?

[grant]

That's a good question.
I don't think there is a great way to stop the server now without an error.

Do you have a recommendation for what could fix this? Simply removing the error?

[grant]

I think we'd need to change the hander to return 0 and not call logAndSendError.

[anishkny]

Hey sorry had forgotten about this. Something like this would be very useful:

npx @google-cloud/functions-framework --run-script "./test-my-api.sh"

This should spin up the API and then run test-my-api.sh (or whatever) and when the script is done, quit the API and marshal back the exit code for CI.

[chrisLeeTW]

@grant I thinks this is very good and simple and elegant solutions for this problem.

[grant]

This should be fixed now on master with #187.