This message was deleted.

Is it possible that an old run against the stack might not have completed? Or a resource fell over between the last time the stack was run and now?

there are no pending locks on the statefile. the manifest shows it as being updated by

v3.22.1

today, which was a refresh i did earlier which completed successfully. i guess i can try rolling back to a previous checkpoint, but that shouldn’t be necessary. i’m happy to dig in more, but there’s absolutely nothing in the logs to indicate what’s going wrong. i’m just running

pulumi preview --debug --logtostderr -v 10

Hm, interesting. I'm going to take that gist back to the engineering team to figure out what's up as I'm not finding anything in there that would explain it either 😕

thanks, laura. i appreciate it

Our engineers asked if you'd open an issue so they can help figure out what's happening and why we aren't producing a better error (why we're not capturing the error to help debug from that layer in the process). Mind raising a flag in https://github.com/pulumi/pulumi/issues/new?assignees=&labels=kind%2Fbug&template=0-bug-report.md and tagging me (https://github.com/nimbinatus) to ensure it gets escalated?

sure thing, will do in a minute

Got it; thanks! I'm passing it on right now

thanks again

You're very welcome! Please let me know if it stalls, and I'll go poking around 😄