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

preview_error_log.sh

Hmm, that’s not good! Any chance you could open an issue on `pulumi/pulumi` with the backtrace and any other context that might be useful for reproducing this?

I actually just opened <https://github.com/pulumi/pulumi/issues/2170> :slightly_smiling_face:.

We've seen some similar issues like this in the past - but this one looks different.

A casual look at the source didn’t suggest anything that might obviously panic

These errors are generally related to unclean teardown of the process.

<@UD2HJDBCL> Curious - does this repro consistently or was it a one off?

Have you seen this panic multiple times?  Or did it just happen once and the same operation succeeded the next time?

looks like removing the yarn lock file and repulling the latest providers fixes it

0.16.2 was pushed 8 days ago (0.16.3 will likely come out shortly)

I had it set to `0.16.1` in my packages file. after setting `pulumi/pulumi` to `latest` is when the bug happened