anyone know what might cause this

Question

stocky-spoon-28903 · Answer

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

white-balloon-205 · Answer

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

stocky-spoon-28903 · Answer

Ah sorry I didn t see that one

stocky-spoon-28903 · Answer

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

white-balloon-205 · Answer

These errors are generally related to unclean teardown of the process

stocky-spoon-28903 · Answer

Makes sense

white-balloon-205 · Answer

< busy umbrella 36067> Curious does this repro consistently or was it a one off

busy-umbrella-36067 · Answer

not sure what you mean < white balloon 205>

white-balloon-205 · Answer

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

busy-umbrella-36067 · Answer

ah it kept recurring

busy-umbrella-36067 · Answer

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

white-balloon-205 · Answer

Interesting okay we ll look into it

busy-umbrella-36067 · Answer

`0 16 2` was just pushed on NPM right

white-balloon-205 · Answer

0 16 2 was pushed 8 days ago 0 16 3 will likely come out shortly

busy-umbrella-36067 · Answer

I had it set to `0 16 1` in my packages file after setting `pulumi pulumi` to `latest` is when the bug happened

white-balloon-205 · Answer

Okay good to know