https://pulumi.com logo
#general
Title
# general
b

busy-umbrella-36067

11/06/2018, 8:16 PM
anyone know what might cause this?
s

stocky-spoon-28903

11/06/2018, 8:44 PM
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?
w

white-balloon-205

11/06/2018, 8:45 PM
I actually just opened https://github.com/pulumi/pulumi/issues/2170 🙂. We've seen some similar issues like this in the past - but this one looks different.
s

stocky-spoon-28903

11/06/2018, 8:46 PM
Ah - sorry I didn’t see that one
A casual look at the source didn’t suggest anything that might obviously panic
w

white-balloon-205

11/06/2018, 8:47 PM
These errors are generally related to unclean teardown of the process.
s

stocky-spoon-28903

11/06/2018, 8:47 PM
Makes sense.
w

white-balloon-205

11/06/2018, 8:47 PM
@busy-umbrella-36067 Curious - does this repro consistently or was it a one off?
b

busy-umbrella-36067

11/06/2018, 8:48 PM
not sure what you mean @white-balloon-205
w

white-balloon-205

11/06/2018, 8:48 PM
Have you seen this panic multiple times? Or did it just happen once and the same operation succeeded the next time?
b

busy-umbrella-36067

11/06/2018, 8:49 PM
ah, it kept recurring
looks like removing the yarn lock file and repulling the latest providers fixes it
w

white-balloon-205

11/06/2018, 8:50 PM
Interesting - okay - we'll look into it.
b

busy-umbrella-36067

11/06/2018, 8:50 PM
0.16.2
was just pushed on NPM right?
w

white-balloon-205

11/06/2018, 8:51 PM
0.16.2 was pushed 8 days ago (0.16.3 will likely come out shortly)
b

busy-umbrella-36067

11/06/2018, 8:52 PM
I had it set to
0.16.1
in my packages file. after setting
pulumi/pulumi
to
latest
is when the bug happened
w

white-balloon-205

11/06/2018, 9:00 PM
Okay - good to know.