No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

```Diagnostics:
  pulumi:pulumi:Stack (compute-b-compute-b-stage-eus2):
    (node:97) UnhandledPromiseRejectionWarning: Error: Failed to load gRPC binary module because it was not installed for the current system
    Expected directory: node-v64-linux-x64-glibc
    Found: [node-v64-darwin-x64-unknown]
    This problem can often be fixed by running "npm rebuild" on the current system
    Original error: Cannot find module '/data/pulumi/node_modules/grpc/src/node/extension_binary/node-v64-linux-x64-glibc/grpc_node.node'
        at Object.&lt;anonymous&gt; (/data/pulumi/node_modules/grpc/src/grpc_extension.js:53:17)
        at Module._compile (internal/modules/cjs/loader.js:689:30)
        at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10)
        at Module.load (internal/modules/cjs/loader.js:599:32)
        at tryModuleLoad (internal/modules/cjs/loader.js:538:12)
        at Function.Module._load (internal/modules/cjs/loader.js:530:3)
        at Module.require (internal/modules/cjs/loader.js:637:17)
        at require (internal/modules/cjs/helpers.js:22:18)
        at Object.&lt;anonymous&gt; (/data/pulumi/node_modules/grpc/src/client_interceptors.js:144:12)
        at Module._compile (internal/modules/cjs/loader.js:689:30)
    (node:97) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)                                                                                                                 
    (node:97) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.                                                                                                                                                             

Resources:
    - 3 to delete```

Was this something you saw only in the preview?  Or did the update also go ahead and do the deletes after reporting this error?  

Both are problems, but the latter would be a very serious issue if you did see that happen.  

I launched it with -y so it did go forward I believe, and yea even with -y I would think it should stop after that error

I can run another test for you, I'll try it a bit later

Opened <https://github.com/pulumi/pulumi/issues/2316>.  If you do happen to be able to reproduce this or get more details, feel free to add them there.

ok i was able to reproduce it.. i’ll post some more info to the issue