b85f95acd9
It is possible for the sub-process responsible for running a NodeJS Pulumi program to exit with a success code before the user's program has run if the process of loading the runtime generates an unhandled promise rejection. These changes fix this by registering the unhandled exception and rejection handlers that are responsible for ensuring a non-zero exit code in these cases before any other action is taken. Note that this issue is really only possible because the Node language host (like the Python language host) is composed of two processes: one that serves the language host gRPC service and one that loads and runs the user's program. The former launches the latter in response to a call to its `Run` gRPC endpoint. The lifetime of the user's program is considered to be bounded by the lifetime of the `Run` invocation. The NodeJS process maintains its own connection to the engine over which resource registrations are communicated. It is tempting to add a message to the resource monitor RPC interface that signals that no further registrations are performed, but this is complicated due to the three-party topology and the possibility that such an RPC may never be sent (e.g. due to a crash or a downlevel version of the Pulumi Node runtime). Fixes #2316. |
||
|---|---|---|
| .. | ||
| index.ts | ||
| run.ts | ||