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

Just upgraded, seeing errors from asyncio saying loop closed

I _suspect_ the invoking code is <https://github.com/dingbots/deplumi/blob/master/deplumi/builders/pipenv.py> and I'm _assuming_ that <https://github.com/pulumi/pulumi/pull/3019> is to blame

but all I know for sure is if I downgrade the pulumi python package from 0.17.28 to 0.17.26, it goes away

Where is the invoke in that code? Nothing jumps out at me...

it's the inner mechanism for a lambda package builder

the "entry points" are <https://github.com/dingbots/deplumi/blob/master/deplumi/__init__.py>

```
handle = self._ready.popleft()
    IndexError: pop from an empty deque
    error: an unhandled error occurred: Program exited with non-zero exit code: 1
```

unfortunately, I haven't spent enough time in the inner guts of `asyncio` to understand it

Is there any way to turn this into a straightforward local repro?

my first guess is long-running tasks/futures?

it might also have to do with all the machinery that goes into process handling?

aside, is `pulumi.export("value", my_async_func())` a good test stand?

like, will it invoke the same pertinent code paths as if i embedded the process into a resource?

`git bisect` puts the blame on Make `pulumi.runtime.invoke` synchronous. (#3019)

so i guess that theory is lightly confirmed

(63eb7abb5949e562b20bf9fe43bac1868e730774)

I filed <https://github.com/pulumi/pulumi/issues/3038> so that there's a note where other people can find that this bug exists

fun fact: i don't actually have to invoke deplumi to trigger the bug, just import it