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

I'm trying to debug this issue I posted a couple days ago.
```Diagnostics:
  pulumi:pulumi:Stack (evilapp-dev):
    error: rpc error: code = Canceled desc = grpc: the client connection is closing```
<https://pulumi-community.slack.com/archives/C84L4E3N1/p1699444003791829>


I saw in this GitHub issue you could enable the Node.js debugger on the `pulumi` program using `NODE_OPTIONS=--inspect-brk`, then attach to the debugger via Chrome DevTools.

This _*kind of*_ works for `pulumi preview` but not at all for `pulumi destroy`.

Does anyone know the best approach for debugging an issue like this?