Channels
announcements
automation-api
aws
azure
blog-posts
built-with-pulumi
cloudengineering
cloudengineering-support
content-share
contribex
contribute
docs
dotnet
finops
general
getting-started
gitlab
golang
google-cloud
hackathon-03-19-2020
hacktoberfest
install
java
jobs
kubernetes
learn-pulumi-events
linen
localstack
multi-language-hackathon
office-hours
oracle-cloud-infrastructure
package-authoring
pulumi-ai
pulumi-cdk
pulumi-cloud
pulumi-crosscode
pulumi-deployments
pulumi-kubernetes-operator
pulumiverse
python
registry
status
testingtesting123
testingtesting321
typescript
welcome
workshops
yaml
Title
b
better-shampoo-48884
03/27/2021, 6:00 PMYeah. progress is killing me today. Every Single Step Hurts.
Error: The Pulumi runtime detected that 904 promises were still active
at the time that the process exited. There are a few ways that this can occur:
* Not using `await` or `.then` on a Promise returned from a Pulumi API
* Introducing a cyclic dependency between two Pulumi Resources
* A bug in the Pulumi Runtimetscts-nodetscts-nodeAnd if you're wondering, yes, pretty much every reference to every resource is listed in the debug info.
b
billowy-army-68599
03/27/2021, 7:08 PMThis sounds like a bug, would you mind filing an issue so we can investigate?
b
better-shampoo-48884
03/27/2021, 8:27 PMWill try to do - but it's also likely that it's because of the way I'm running my stuff. will try to get a reproducable new stack thing going, just running low on networks I can use for testing.
And.. this is weird.. but afaik this is only reproducible when I'm running automation through an azure pipeline 😕
https://github.com/pulumi/pulumi/issues/6633 created. It's going to a be a pain to reproduce I fear.. that is - I can reproduce it every time, but it's just a pain to get anything set up with azure pipelines 😄